Accessory-based storage for use with a medical device

ABSTRACT

A patient-coupled resuscitation device for use with a plurality of medical devices is provided. The resuscitation device includes a portion configured to provide treatment, a connector configured to connect the resuscitation device to one of a first medical device and a second medical device, and a housing including a memory and associated circuitry. The memory and associated circuitry is configured to store a device identifier to identify the resuscitation device; receive medical treatment information from the first medical device, the medical treatment information including at least one of: patient physiological data, patient characteristic data, and rescuer performance data; receive timing information of the medical treatment information from the first medical device; record the medical treatment information and the timing information; and transfer, upon detecting a connection to the second medical device, the medical treatment information and the timing information to the second medical device.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.17/098,676 (filed 16 Nov. 2020), which claims the benefit of U.S.Provisional Patent Application 62/935,849 (filed 15 Nov. 2019). Allsubject matter set forth in each of the above-referenced applications ishereby incorporated by reference in its entirety into the presentapplication as if fully set forth herein.

BACKGROUND

Treatment of a subject experiencing cardiac distress can generallyinclude one or more of clearing the subject's airway, assisting thesubject's breathing, providing chest compressions, and providingdefibrillation or other similar treatment shocks. The treatment can beprovided using one or more medical devices and medical deviceaccessories such as a patient-coupled resuscitation device.

Assisting the subject's breathing can be performed using, for example, aventilator including a manual ventilation device such as a bag-valvemask or an automatic ventilation device. The ventilator can include oneor more sensors to detect, for example, air flow rate into the subject'slungs. Providing chest compressions can be performed using a chestcompression sensor configured to measure, for example, chest compressionrate and depth of compression information. Defibrillation can beperformed with the use of an automatic external defibrillator (AED)Several commercially available automatic external defibrillators aresemi-automatic external defibrillators (SAED), which require a responderto press a button to initiate a defibrillation shock. After thedefibrillator analyzes the subject's condition and determines that thesubject's electrical heart rhythm is shockable, the defibrillatorprovides an indication that the rhythm is shockable yet refrains fromproviding a shock until the user intervenes (e.g., presses shockbutton). Fully automatic external defibrillators, on the other hand, donot wait for user intervention before applying shocks. As the term isused herein, automatic external defibrillators (AED) includesemi-automatic external defibrillators (SAED). A defibrillator may havemonitoring capabilities, and so can include one or more sensorsconfigured to measure various physiological data for the patient as wellas information related to any treatment shocks delivered to the patient.Each medical device and/or accessory associated with treatment of asubject can be configured to record information collected duringtreatment for later analysis, the information including specifics onwhat treatment the subject received and/or performance data about anymedical personnel providing the treatment.

SUMMARY

In an example, a patient-coupled resuscitation device for use with aplurality of medical devices is provided. The patient-coupledresuscitation device includes a patient-coupled portion configured toprovide resuscitative treatment to the patient, a connector configuredto electrically connect the patient-coupled resuscitation device to atleast one of a first medical device and a second medical device, and ahousing including a non-volatile memory and associated circuitry. Thenon-volatile memory and associated circuitry is configured to store adevice identifier readable by the first medical device and the secondmedical device to identify the patient-coupled resuscitation device;receive medical treatment information from the first medical device viathe connector, the medical treatment information including at least oneof: patient physiological data, patient characteristic data, and rescuerperformance data; receive timing information of the medical treatmentinformation from the first medical device via the connector; record themedical treatment information and the timing information; and transfer,upon detecting an electrical connection to the second medical device,the medical treatment information and the timing information to thesecond medical device.

Implementations of the patient-coupled resuscitation device for use witha plurality of medical devices can include one or more of the followingfeatures.

In examples of the patient-coupled resuscitation device, the medicaltreatment information can be recorded by the first medical device duringmonitoring of a patient prior to and/or during treatment of the patient.

In some examples of the patient-coupled resuscitation device, thepatient-coupled resuscitation device can include a sensor configured toacquire at least a portion of the medical treatment information.

In examples of the patient-coupled resuscitation device, the deviceidentifier can include type and serial information for at least one ofthe first medical device and the second medical device to record.

In examples of the patient-coupled resuscitation device, the deviceidentifier can provide for authentication with at least one of the firstmedical device and the second medical device for secure transfer of themedical treatment information.

In examples of the patient-coupled resuscitation device, the timinginformation of the medical treatment information can include a time atwhich the medical treatment information was recorded by the firstmedical device. In some examples, the resuscitation device can includetiming circuitry operable to independently track time elapsed since thetime at which the medical treatment information was recorded by thefirst medical device. In some examples, the timing circuitry can includea power source and at least one of: a real-time clock and a counter.

In examples of the patient-coupled resuscitation device, the timinginformation of the medical treatment information can provide a basis fortime alignment between the first medical device and the second medicaldevice.

In examples of the patient-coupled resuscitation device, thenon-volatile memory and associated circuitry can be configured to recordthe medical treatment information and the timing information from thefirst medical device before the transfer of the medical treatmentinformation and the timing information to the second medical device. Insome examples, the non-volatile memory and associated circuitry can beconfigured to record the medical treatment information and the timinginformation from the first medical device when the connector is engagedwith the first medical device, and transfer of the medical treatmentinformation and the timing information to the second medical device whenthe connector is engaged with the second medical device.

In examples of the patient-coupled resuscitation device, the timinginformation can include at least one of: a time at which the connectoris engaged with the first medical device and a time at which theconnector is engaged with the second medical device.

In examples of the patient-coupled resuscitation device, the medicaltreatment information can further include summary information recordingcritical patient events requiring treatment, shock information for anydelivered shocks, pacing summary data, and indications of alarm events.

In some examples of the patient-coupled resuscitation device, thepatient-coupled resuscitation device can include an electrode configuredto be operably coupled with the first medical device via the connectorduring a first treatment event and to record at least one parameterassociated with a treatment course delivered to the patient during thefirst treatment event to the non-volatile memory. In some examples, theelectrode can be further configured to be decoupled from the firstmedical device and operably coupled to the second medical device via theconnector such that the medical treatment information stored on thenon-volatile memory is accessible to the second medical device. In someexamples, the electrode can include a defibrillation electrode, thefirst medical device can include a first defibrillator and/or a firstpatient monitor and the second medical device can include a seconddefibrillator and/or a second patient monitor. In some examples, thepatient physiological data can include electrocardiogram (ECG) data forthe patient acquired prior to treatment, during treatment, and/or aftertreatment. In some examples, the ECG data can include ECG dataassociated with at least one of a treatable cardiac rhythm and anon-treatable cardiac rhythm.

In some examples of the patient-coupled resuscitation device, thepatient-coupled resuscitation device can include a flow sensorconfigured to be operably coupled with the first medical device via theconnector during a first treatment event and to record at least oneparameter associated with the first treatment event to the memory.

In examples of the patient-coupled resuscitation device, the flow sensorcan be configured to be decoupled from the first medical device via theconnector and operably coupled to the second medical device such thatthe medical treatment information stored on the memory is accessible tothe second medical device. In some examples, the first medical devicecan include a first defibrillator and/or a first patient monitor and thesecond medical device can include a second defibrillator, a secondpatient monitor and/or a ventilator. In some examples, the physiologicaldata can include end-tidal CO2 data for the patient acquired prior totreatment, during treatment, and/or after treatment. In some examples,the first medical device can include a defibrillator and the secondmedical device can include a ventilator. In some examples, the firstmedical device can include a ventilator and the second medical devicecan include a defibrillator.

In examples of the patient-coupled resuscitation device, the firstmedical device can include a first defibrillator and the second medicaldevice can include a second defibrillator.

In some examples of the patient-coupled resuscitation device, thepatient-coupled resuscitation device can include a chest compressiondevice configured to monitor one or more cardiopulmonary resuscitation(CPR) parameters associated with CPR being administered to the patient,and can be further configured to record the one or more CPR parametersto the memory. In some examples, the one or more CPR parameters caninclude one or more of chest compression rate information, chestcompression depth information, and chest compression releaseinformation. In some examples, the chest compression monitoring devicecan further include a strap configured to be placed about a torso of thepatient to maintain the chest compression monitoring device in position.In some examples, the strap can include one or more sensors configuredto measure at least one additional parameter during monitoring andtreatment of the patient. In some examples, the one or more sensors caninclude an accelerometer configured to measure compression depthinformation during treatment of the patient, and wherein the at leastone additional parameter includes compression depth information.

In some examples of the patient-coupled resuscitation device, thepatient-coupled resuscitation device can include a battery configured tooperably couple with and provide power to any medical device of theplurality of medical devices. In some examples, the medical treatmentinformation can include device operational information includinginformation about the battery and the medical device being powered bythe battery. In some examples, the device operational information caninclude one or more of a number of minutes the battery has been used, anumber of defibrillation treatment shocks have been delivered by thedevice being powered by the battery, information related to additionaloperational modes performed by the device being powered by the battery,and errors associated with the device being powered by the battery.

In some examples of the patient-coupled resuscitation device, thepatient-coupled resuscitation device can be configured to be operablyremoved from a first of the plurality of medical devices and operablycoupled to a second of the plurality of medical devices.

In some examples of the patient-coupled resuscitation device, thepatient-coupled resuscitation device can be configured to be operablyremoved from a first of the plurality of medical devices and operablycoupled to a computing device.

In examples of the patient-coupled resuscitation device, thenon-volatile memory and associated circuitry further configured todetermine whether the resuscitation device is within a proximity of aremote device, establish, in response to a determination that theresuscitation device is within the proximity, an operable connectionwith the remote device, and transfer at least a portion of the medicaltreatment information to the remote device. In some examples, thetransfer of at least a portion of the medical treatment information tothe remote device can occur automatically when the operable connectionis established between the resuscitation device and the remote device.In some examples, the transfer of at least a portion of the medicaltreatment information to the remote device can occur in response to auser-provided request to transfer subsequent to establishing theoperable connection between the resuscitation device and the remotedevice.

In examples of the patient-coupled resuscitation device, thenon-volatile memory can be integrated into the connector.

In examples of the patient-coupled resuscitation device, recording themedical treatment device information to the memory can includeencrypting the medical treatment information prior to recording to thememory.

In examples of the patient-coupled resuscitation device, the patientphysiological data can include one or more of patient ECG data, heartrate data, ECG waveform data, end-tidal CO2 data, CO2 waveform data,pulse oximetry data, blood oxygenation data, blood pressure data, andrespiratory rate data.

In examples of the patient-coupled resuscitation device, the patientcharacteristic data can include one or more of patient height data,patient weight data, patient gender indication, patient physicalmeasurement data, and patient history information.

In examples of the patient-coupled resuscitation device, the rescuerperformance data can include one or more of chest compressionperformance data, ventilation performance data, rescuer treatmentinformation, and drug infusion information.

In examples of the patient-coupled resuscitation device, the medicaltreatment information can include device operational data including oneor more of defibrillation shock delivery information, defibrillationshock energy information, and ventilator flow information.

In another example, a second patient-coupled resuscitation device foruse with a plurality of medical devices is provided. The secondpatient-coupled resuscitation device includes a patient-coupled portionconfigured to provide resuscitative treatment to the patient and ahousing including a wireless communications interface and associatedcircuitry and a non-volatile memory and associated circuitry. Thewireless communications interface and associated circuitry is configuredto detect and establish a short-range wireless connection with a firstmedical device and detect and establish, at a subsequent time, ashort-range wireless connection with a second medical device. Thenon-volatile memory and associated circuitry is configured to store adevice identifier readable by the first medical device and the secondmedical device to identify the patient-coupled resuscitation device;receive and record, upon the short-range wireless connection with thefirst medical device being established, medical treatment informationfrom the first medical device, the medical treatment informationincluding at least one of patient physiological data, patientcharacteristic data, and rescuer performance data; and transfer, upondetecting the short-range wireless connection with the second medicaldevice, the medical treatment information to the second medical device.

Implementations of the second patient-coupled resuscitation device foruse with a plurality of medical devices can include one or more of thefollowing features.

In examples of the second patient-coupled resuscitation device, theshort-range wireless connection with the first medical device or thesecond medical device can include a wireless protocol involving at leastone of Bluetooth, Zigbee, near field communication, ultra-wideband, andinfrared.

In examples of the second patient-coupled resuscitation device, themedical treatment information can be recorded by the first medicaldevice during monitoring of a patient prior to and/or during treatmentof the patient.

In examples of examples of the second patient-coupled resuscitationdevice, the second patient-coupled resuscitation device can furtherinclude a sensor configured to acquire at least a portion of the medicaltreatment information.

In examples of the second patient-coupled resuscitation device, thedevice identifier can include type and serial information for at leastone of the first medical device and the second medical device to record.

In examples of the second patient-coupled resuscitation device, thedevice identifier can provide for authentication with at least one ofthe first medical device and the second medical device for securetransfer of the medical treatment information.

In examples of the second patient-coupled resuscitation device, thenon-volatile memory and associated circuitry can be configured toreceive timing information of the medical treatment information from thefirst medical device via the wireless communications interface. In someexamples, the timing information of the medical treatment informationcan include a time at which the medical treatment information wasrecorded by the first medical device. In some examples, the secondpatient-coupled resuscitation device can include timing circuitryoperable to independently track time elapsed since the time at which themedical treatment information was recorded by the first medical device.In some examples, the timing circuitry can include a power source and atleast one of: a real-time clock and a counter. In some examples, thetiming information of the medical treatment information can provide abasis for time alignment between the first medical device and the secondmedical device. In some examples, the timing information can include atleast one of: a time at which the short-range wireless connection isestablished with the first medical device and a time at which theshort-range wireless connection is established with the second medicaldevice.

In examples of the second patient-coupled resuscitation device, thenon-volatile memory and associated circuitry can be configured to recordthe medical treatment information from the first medical device beforethe transfer of the medical treatment information to the second medicaldevice. In some examples, the non-volatile memory and associatedcircuitry can be configured to record the medical treatment informationfrom the first medical device when the short-range wireless connectionis established with the first medical device, and transfer of themedical treatment information to the second medical device when theshort-range wireless connection is established with the second medicaldevice.

In examples of the second patient-coupled resuscitation device, themedical treatment information can further include summary informationrecording critical patient events requiring treatment, shock informationfor any delivered shocks, pacing summary data, and indications of alarmevents.

In some examples of the second patient-coupled resuscitation device, thesecond patient-coupled resuscitation device can include an electrodeconfigured to be operably coupled with the first medical device during afirst treatment event and to record at least one parameter associatedwith a treatment course delivered to the patient during the firsttreatment event to the non-volatile memory. In some examples, theelectrode can be further configured to be decoupled from the firstmedical device and operably coupled to the second medical device suchthat the medical treatment information stored on the non-volatile memoryis accessible to the second medical device. In some examples, theelectrode can include a defibrillation electrode, the first medicaldevice can include a first defibrillator and/or a first patient monitorand the second medical device can include a second defibrillator and/ora second patient monitor. In some examples, the patient physiologicaldata can include ECG data for the patient acquired prior to treatment,during treatment, and/or after treatment. In some examples, the ECG datacan include ECG data associated with at least one of a treatable cardiacrhythm and a non-treatable cardiac rhythm.

In some examples of the second patient-coupled resuscitation device, thesecond patient-coupled resuscitation device can include a flow sensorconfigured to be operably coupled with the first medical device during afirst treatment event and to record at least one parameter associatedwith the first treatment event to the memory. In some examples, thephysiological data can include end-tidal CO2 data for the patientacquired prior to treatment, during treatment, and/or after treatment.In some examples, the flow sensor can be configured to be decoupled fromthe first medical device and operably coupled to the second medicaldevice such that the medical treatment information stored on the memoryis accessible to the second medical device. In some examples, the firstmedical device can include a first defibrillator a first patient monitorand/or a first ventilator, and the second medical device can include asecond defibrillator, a second patient monitor and/or a secondventilator. In some examples, the first medical device can include adefibrillator and the second medical device can include a ventilator. Insome examples, the first medical device can include a ventilator and thesecond medical device can include a defibrillator.

In examples of the second patient-coupled resuscitation device, thefirst medical device can include a first defibrillator and the secondmedical device can include a second defibrillator.

In some examples of the second patient-coupled resuscitation device, thesecond patient-coupled resuscitation device can include a chestcompression device configured to monitor one or more cardiopulmonaryresuscitation (CPR) parameters associated with CPR being administered tothe patient, and further configured to record the one or more CPRparameters to the memory. In some examples, the one or more CPRparameters can include one or more of chest compression rateinformation, chest compression depth information, and chest compressionrelease information. In some examples, the chest compression device canfurther include a strap configured to be placed about a torso of thepatient to maintain the chest compression device in position. In someexamples, the strap can include one or more sensors configured tomeasure at least one additional parameter during monitoring andtreatment of the patient. In some examples, the one or more sensors caninclude an accelerometer configured to measure compression depthinformation during treatment of the patient, and wherein the at leastone additional parameter includes compression depth information.

In some examples of the second patient-coupled resuscitation device, thesecond patient-coupled resuscitation device can include a batteryconfigured to operably couple with and provide power to any medicaldevice of the plurality of medical devices. In some examples, themedical treatment information can include device operational informationincluding information about the battery and the medical device beingpowered by the battery. In some examples, the device operationalinformation can include one or more of a number of minutes the batteryhas been used, a number of defibrillation treatment shocks have beendelivered by the device being powered by the battery, informationrelated to additional operational modes performed by the device beingpowered by the battery, and errors associated with the device beingpowered by the battery.

In some examples of the second patient-coupled resuscitation device, thesecond patient-coupled resuscitation device can be further configured tobe operably removed from a first of the plurality of medical devices andoperably coupled to a second of the plurality of medical devices.

In some examples of the second patient-coupled resuscitation device, thesecond patient-coupled resuscitation device can be further configured tobe operably removed from a first of the plurality of medical devices andoperably coupled to a computing device.

In examples of the second patient-coupled resuscitation device, thenon-volatile memory and associated circuitry can be further configuredto determine whether the resuscitation device is within a proximity of aremote device, establish, in response to a determination that theresuscitation device is within the proximity, an operable connectionwith the remote device, and transfer at least a portion of the medicaltreatment information to the remote device. In some examples, thetransfer of at least a portion of the medical treatment information tothe remote device can occur automatically when the operable connectionis established between the resuscitation device and the remote device.In some examples, the transfer of at least a portion of the medicaltreatment information to the remote device can occur in response to auser-provided request to transfer subsequent to establishing theoperable connection between the resuscitation device and the remotedevice.

In examples of the second patient-coupled resuscitation device,recording the medical treatment device information to the memory caninclude encrypting the medical treatment information prior to recordingto the memory.

In examples of the second patient-coupled resuscitation device, thepatient physiological data can include one or more of patient ECG data,heart rate data, ECG waveform data, end-tidal CO2 data, CO2 waveformdata, pulse oximetry data, blood oxygenation data, blood pressure data,and respiratory rate data.

In examples of the second patient-coupled resuscitation device, thepatient characteristic data can include one or more of patient heightdata, patient weight data, patient gender indication, patient physicalmeasurement data, and patient history information.

In examples of the second patient-coupled resuscitation device, therescuer performance data can include one or more of chest compressionperformance data, ventilation performance data, rescuer treatmentinformation, and drug infusion information.

In examples of the second patient-coupled resuscitation device, themedical treatment information can include device operational dataincluding one or more of defibrillation shock delivery information,defibrillation shock energy information, and ventilator flowinformation.

In examples of the second patient-coupled resuscitation device, thewireless communications interface and associated circuitry can beconfigured to establish the short-range wireless connections with thefirst medical device and the second device successively.

In examples of the second patient-coupled resuscitation device, thewireless communications interface and associated circuitry can beconfigured to establish the short-range wireless connections with thefirst medical device and the second device simultaneously.

In another example, a medical treatment device for managing medicaltreatment information is provided. The medical treatment device includesat least one sensor configured to obtain medical data, a batteryincluding a non-volatile memory and associated circuitry configured tostore medical device information, a receptacle to which the battery isremovably coupled and configured to draw power from the battery, and atleast one processor coupled to the at least one sensor and the battery.The at least one processor is configured to receive the medical datafrom the at least one sensor, process the medical data to generatemedical treatment information, the medical treatment informationincluding at least one of: patient physiological data, patientcharacteristic data, and rescuer performance data, and record themedical treatment information to the non-volatile memory of the battery.

Implementations of the medical treatment device for managing medicaltreatment information can include one or more of the following features.

In examples of the medical treatment device, the medical treatmentdevice information can further include device operational information.In some examples, the device operational information can include one ormore of a number of minutes the battery has been used, a number oftreatment shocks have been delivered by the medical treatment devicewhen powered by the battery, information related to additionaloperational modes performed by the medical treatment device when poweredby the battery, and errors associated with the medical treatment devicewhen powered by the battery.

In examples of the medical treatment device, the at least one sensor caninclude a defibrillation electrode configured to be operably coupledwith the monitor during a first treatment event and to record at leastone parameter associated with the first treatment event. In someexamples, the patient physiological data can include ECG data for thepatient acquired prior to treatment, during treatment, and/or aftertreatment. In some examples, the ECG data can include ECG dataassociated with at least one of a treatable cardiac rhythm and anon-treatable cardiac rhythm.

In examples of the medical treatment device, the at least one sensor caninclude a chest compression monitoring device configured to monitor oneor more CPR parameters associated with CPR being administered to thepatient. In some examples, the at least one processor can be furtherconfigured to record the one or more CPR parameters to the memory. Insome examples, the one or more CPR parameters can include at least oneof chest compression rate information, chest compression depthinformation, and chest compression release information.

In examples of the medical treatment device, the memory can beconfigured to be operably removed from the battery and operably coupledto a second device.

In examples of the medical treatment device, the at least one processorcan be further configured to determine if the medical treatment deviceis within a proximity of a remote device, establish an operableconnection with the remote device, and transfer at least a portion ofthe medical treatment device information from the memory to the remotedevice. In some examples, the transfer of at least a portion of themedical treatment device information to the remote device can occurautomatically when the operable connection is established between themedical treatment device and the remote device. In some examples, thetransfer of at least a portion of the medical treatment deviceinformation to the remote device can occur in response to auser-provided request to transfer when the operable connection isestablished between the medical treatment device and the remote device.

In examples of the medical treatment device, the memory can beintegrated into a connector of the battery.

In another example, a standalone chest compression device for use with aplurality of medical treatment devices is provided. The chestcompression device includes a housing, a non-volatile memory andassociated circuitry disposed in the housing, at least one motion sensorconfigured to detect chest motion information during performance ofchest compressions by a rescuer, a communication circuit disposed in thehousing and configured to establish a communicative connection with amedical device, and at least one processor disposed in the housing andoperably coupled to the non-volatile memory, the at least one motionsensor, and the communication circuit. The at least one processor isconfigured to receive the chest motion information from the at least onemotion sensor; establish the communicative connection with the medicaldevice; receive medical treatment information from the medical device,the medical treatment information including at least one of: patientphysiological data, patient characteristic data and rescuer performancedata; record the chest motion information and the medical treatmentinformation to the non-volatile memory; and transfer the chest motioninformation to the medical device.

Implementations of the standalone chest compression device for use witha plurality of medical treatment devices can include one or more of thefollowing features.

In examples of the standalone chest compression device, the at least oneprocessor can be configured to receive the medical treatment informationfrom the medical device via the communicative connection.

In some examples of the standalone chest compression device, thestandalone chest compression device can include at least one computingdevice configured to store the medical treatment information, and the atleast one processor can be configured to establish a communicativeconnection with the at least one computing device to receive and recordthe medical treatment information to the memory. In some examples, theat least one computing device can include a user interface for inputtingthe medical treatment information.

In some examples of the standalone chest compression device, thestandalone chest compression device can include a connector coupled withthe communication circuit and for mechanical coupling and decouplingwith the medical device, and for establishing the communicativeconnection with the medical device.

In some examples of the standalone chest compression device, thestandalone chest compression device can include a wirelesscommunications interface and associated circuitry coupled with thecommunication circuit and configured to detect and establish ashort-range wireless connection with the medical device. In someexamples, the short-range wireless connection with the medical devicecan include a wireless protocol involving at least one of: Bluetooth,Zigbee, near field communication, ultra-wideband, and infrared.

In examples of the standalone chest compression device, the at least oneprocessor can be configured to generate one or more CPR parameters basedon the chest motion information. In some examples, the at least oneprocessor is configured to compare the one or more CPR parameters withdesired target parameters to generate a comparison and provide anindication of CPR quality based on the comparison. In some examples, thestandalone chest compression device can include a feedback deviceconfigured to provide an indication of the one or more CPR parameters.In some examples, the standalone chest compression device can include afeedback device configured to provide an indication of the comparisonbetween the one or more CPR parameters and the desired targetparameters. In some examples, the one or more CPR parameters can includeat least one of chest compression rate information, chest compressiondepth information, and chest compression release information.

In examples of the standalone chest compression device, the at least oneprocessor can be provided within space enclosed by the housing.

In examples of the standalone chest compression device, the at least oneprocessor can be provided with the medical device.

In some examples of the standalone chest compression device, thestandalone chest compression device can further include a strapconfigured to be placed about a torso of the patient to hold the chestcompression device in position. In some examples, the strap can includeone or more second sensors configured to measure at least one additionalparameter during monitoring and treatment of the patient. In someexamples, the one or more second sensors can include a strain gaugeconfigured to measure expansion and contraction of the patient's torsoduring monitoring and treatment of the patient, and wherein the at leastone additional parameter includes chest expansion and contractioninformation. In some examples, the at least one processor can be furtherconfigured to record the chest expansion and contraction information tothe memory. In some examples, the at least one processor can be furtherconfigured to determine respiration information for the patient basedupon the chest expansion and contraction information and record therespiration information to the memory. In some examples, the straingauge can include a potentiometer configured to measure changes in alength of at least a portion of the strap when positioned about thetorso of the patient. In some examples, the strap can include anadjustable connector to alter a length of the strap to position the oneor more second sensors on an opposite side of the patient from the atleast one sensor. In some examples, the adjustable connector can includeat least one of a buckle, an elastic portion, an adjustablehook-and-loop fastener, a slidable connector, a snap connector, and aratcheting connector. In some examples, the strap can include areceptacle configure to receive at least a portion of the chestcompression device to secure the chest compression device against thetorso of the patient.

In some examples of the standalone chest compression device, thestandalone chest compression device can be configured to be activatedupon removal from a package.

In some examples of the standalone chest compression device, thestandalone chest compression device can be configured to be activated inresponse to a force being exerted on at least a portion of the chestcompression device.

In some examples of the standalone chest compression device, thestandalone chest compression device can be configured to be activated inresponse to a user-actuation of at least a portion of the chestcompression device.

In some examples of the standalone chest compression device, thestandalone chest compression device can be configured to be activated inresponse to being moved into proximity of a defibrillation device.

In examples of the standalone chest compression device, the patientcharacteristic data can include one or more of patient height data,patient weight data, patient gender indication, and patient physicalmeasurement data. In some examples, the at least one processor can befurther configured to determine target compression and/or ventilationparameters based upon the patient characteristic data. In some examples,the at least one processor is configured to compare one or more CPRparameters with the target compression and/or ventilation parameters togenerate a comparison and provide an indication of CPR quality based onthe comparison.

In another example, a defibrillation electrode for use with a pluralityof defibrillation devices is provided. The defibrillation electrodeincludes a connector configured to operably couple the defibrillationelectrode to at least one of a first defibrillation device and a seconddefibrillation device, a skin contacting portion configured to contactskin of a patient, and a housing including non-volatile memory andassociated circuitry. The non-volatile memory and associated circuitryare configured to store a device identifier readable by the firstdefibrillation device and the second defibrillation device to identifythe defibrillation electrode; receive medical treatment information fromthe first defibrillation device via the connector, the medical treatmentinformation including at least one of: patient physiological data,patient characteristic data, and rescuer performance data; record themedical treatment information; and transfer, upon detecting anelectrical connection to the second defibrillation device, the medicaltreatment information to the second defibrillation device.

Implementation of the defibrillation electrode for use with a pluralityof defibrillation devices can include one or more of the followingfeatures.

In examples of the defibrillation electrode, the medical treatmentinformation can be recorded by the first defibrillation device duringmonitoring of a patient prior to and/or during treatment of the patient.

In examples of the defibrillation electrode, the device identifier caninclude type and serial information for at least one of the firstdefibrillation device and the second defibrillation device to record.

In examples of the defibrillation electrode, the device identifier canprovide for authentication with at least one of the first defibrillationdevice and the second defibrillation device for secure transfer of themedical treatment information.

In examples of the defibrillation electrode, the non-volatile memory andassociated circuitry can be configured to receive timing information ofthe medical treatment information from the first defibrillation devicevia the connector. In some examples, the timing information of themedical treatment information can include a time at which the medicaltreatment information was recorded by the first defibrillation device.In some examples, the defibrillation electrode can further includetiming circuitry operable to independently track time elapsed since thetime at which the medical treatment information was recorded by thefirst defibrillation device.

In examples of the defibrillation electrode, the non-volatile memory andassociated circuitry can be configured to record the medical treatmentinformation from the first defibrillation device before the transfer ofthe medical treatment information to the second defibrillation device.In some examples, the non-volatile memory and associated circuitry canbe configured to record the medical treatment information from the firstdefibrillation device when the connector is engaged with the firstdefibrillation device, and transfer of the medical treatment informationto the second defibrillation device when the connector is engaged withthe second defibrillation device.

In examples of the defibrillation electrode, the medical treatmentinformation can further include summary information recording criticalpatient events requiring treatment, shock information for any deliveredshocks, pacing summary data, and indications of alarm events.

In some examples of the defibrillation electrode, the defibrillationelectrode can be configured to be operably removed from a first of theplurality of defibrillation devices and operably coupled to a computingdevice.

In examples of the defibrillation electrode, the non-volatile memory andassociated circuitry can be further configured to determine whether thedefibrillation electrode is within a proximity of a remote device,establish, in response to a determination that the defibrillationelectrode is within the proximity, an operable connection with theremote device, and transfer at least a portion of the medical treatmentinformation to the remote device. In some examples, the transfer of atleast a portion of the medical treatment information to the remotedevice can occur automatically when the operable connection isestablished between the defibrillation electrode and the remote device.In some examples, the transfer of at least a portion of the medicaltreatment information to the remote device can occur in response to auser-provided request to transfer subsequent to establishing theoperable connection between the defibrillation electrode and the remotedevice.

In examples of the defibrillation electrode, recording the medicaltreatment device information to the memory can include encrypting themedical treatment information prior to recording to the memory.

In examples of the defibrillation electrode, the patient physiologicaldata can include one or more of patient ECG data, heart rate data, ECGwaveform data, end-tidal CO2 data, CO2 waveform data, pulse oximetrydata, blood oxygenation data, blood pressure data, and respiratory ratedata.

In examples of the defibrillation electrode, the patient characteristicdata can include one or more of patient height data, patient weightdata, patient gender indication, patient physical measurement data, andpatient history information.

In examples of the defibrillation electrode, the rescuer performancedata can include one or more of chest compression performance data,ventilation performance data, rescuer treatment information, and druginfusion information.

In examples of the defibrillation electrode, the medical treatmentinformation can include device operational data including one or more ofdefibrillation shock delivery information, defibrillation shock energyinformation, and ventilator flow information.

In examples of the defibrillation electrode, the connector can beconfigured to be operably coupled to the defibrillation device during afirst treatment event and the at least one of a processor operablycoupled to the memory and software is further configured to record atleast one parameter associated with the first treatment event to thememory. In some examples, the connector can be further configured to bedecoupled from the defibrillation device and operably coupled to asecond defibrillation device such that the medical treatment informationstored on the memory is accessible to the second defibrillation device.

In examples of the defibrillation electrode, the memory can beconfigured to be operably removed from the defibrillation electrode andoperably coupled to a second defibrillation electrode.

In examples of the defibrillation electrode, the memory can beconfigured to be operably removed from the defibrillation electrode andoperably coupled to a computing device.

In examples of the defibrillation electrode, the memory can beintegrated into the connector.

In examples of the defibrillation electrode, at least a portion of theskin contacting portion can be further configured to deliver adefibrillation shock to the patient during treatment.

In another example, a system for assisting in medical treatment of apatient and for managing medical treatment information is provided. Thesystem includes a patient-coupled resuscitation device including anon-volatile memory and associated circuitry configured to store adevice identifier readable by a plurality of medical devices to identifythe patient-coupled resuscitation device and record medical treatmentinformation including at least one of: patient physiological data,patient characteristic data, and rescuer performance data; a firstmedical device including at least one first processor configured toreceive and record the medical treatment information including at leastone of: patient physiological data, patient characteristic data, andrescuer performance data, establish a first communicative connectionwith the patient-coupled resuscitation device, transfer the medicaltreatment information to the patient-coupled resuscitation device viathe first communicative connection; and a second medical deviceincluding at least one second processor configured to establish a secondcommunicative connection with the patient-coupled resuscitation deviceand receive and record the medical treatment information from thepatient-coupled resuscitation device via the second communicativeconnection.

Implementations of the system for assisting in medical treatment and formanaging medical treatment information can include one or more of thefollowing features.

In examples of the system, the patient-coupled resuscitation device caninclude a connector configured to electrically connect thepatient-coupled resuscitation device to at least one of the firstmedical device and the second medical device.

In examples of the system, the patient-coupled resuscitation device caninclude a wireless communications interface and associated circuitryconfigured to detect and establish a short-range wireless connectionwith the first medical device and detect and establish a short-rangewireless connection with the second medical device.

In some examples, the wireless communications interface and associatedcircuitry can be configured to establish the short-range wirelessconnections with the first medical device and the second devicesuccessively. In some examples, the wireless communications interfaceand associated circuitry can be configured to establish the short-rangewireless connections with the first medical device and the second devicesimultaneously. In some examples, the non-volatile memory and associatedcircuitry of the patient-coupled resuscitation device can be configuredto receive timing information of the medical treatment information fromthe first medical device via the wireless communications interface. Insome examples, the system can include timing circuitry operable toindependently track time elapsed since the time at which the medicaltreatment information was recorded by the first medical device.

In examples of the system, the medical treatment information can berecorded by the first medical device during monitoring of a patientprior to and/or during treatment of the patient.

In examples of the system, the medical treatment information can furtherinclude summary information recording critical patient events requiringtreatment, shock information for any delivered shocks, pacing summarydata, and indications of alarm events.

In examples of the system, the patient-coupled resuscitation device caninclude an electrode configured to be operably coupled with the firstmedical device during a first treatment event and to record at least oneparameter associated with a treatment course delivered to the patientduring the first treatment event to the non-volatile memory. In someexamples, the electrode can include a defibrillation electrode, thefirst medical device can include a first defibrillator and/or a firstpatient monitor and the second medical device can include a seconddefibrillator and/or a second patient monitor.

In examples of the system, the patient physiological data can includeECG data for the patient acquired prior to treatment, during treatment,and/or after treatment.

In examples of the system, the patient-coupled resuscitation device caninclude a flow sensor configured to be operably coupled with the firstmedical device during a first treatment event and to record at least oneparameter associated with the first treatment event to the memory. Insome examples, the first medical device can include a firstdefibrillator and/or a first patient monitor and the second medicaldevice can include a second defibrillator, a second patient monitorand/or a ventilator.

In examples of the system, the first medical device can include a firstdefibrillator and the second medical device can include a seconddefibrillator.

In examples of the system, the patient-coupled resuscitation device caninclude a chest compression device configured to monitor one or more CPRparameters associated with CPR being administered to the patient, andfurther configured to record the one or more CPR parameters to thememory.

In examples of the system, the patient-coupled resuscitation device caninclude a battery configured to operably couple with and provide powerto any of the first medical device and the second medical device. Insome examples, the medical treatment information can include deviceoperational information including information about the battery and themedical device being powered by the battery.

In examples of the system, the patient physiological data can includeone or more of patient ECG data, heart rate data, ECG waveform data,end-tidal CO2 data, CO2 waveform data, pulse oximetry data, bloodoxygenation data, blood pressure data, and respiratory rate data.

In examples of the system, the patient characteristic data can includeone or more of patient height data, patient weight data, patient genderindication, patient physical measurement data, and patient hi storyinformation.

In examples of the system, the rescuer performance data can include oneor more of chest compression performance data, ventilation performancedata, rescuer treatment information, and drug infusion information.

BRIEF DESCRIPTION OF THE DRAWINGS

Various aspects of at least one example are discussed below withreference to the accompanying figures, which are not intended to bedrawn to scale. The figures are included to provide an illustration anda further understanding of the various aspects and examples disclosedherein and are incorporated in and constitute a part of thisspecification. However, the figures are not intended to limit the scopeof the disclosure. The figures, together with the remainder of thespecification, serve to explain principles and operations of thedescribed and claimed aspects and examples. In the figures, eachidentical or nearly identical component that is illustrated in variousfigures is represented by a like numeral. For purposes of clarity, notevery component may be labeled in every figure.

FIG. 1 is a schematic diagram showing a sample medical device and a setof medical device accessories, in accordance with at least one exampledisclosed herein.

FIG. 2 is a schematic diagram showing an alternative sample medicaldevice and a set of medical device accessories, in accordance with atleast one example disclosed herein.

FIG. 3A is a schematic diagram showing a battery being transferredbetween medical devices, in accordance with at least one exampledisclosed herein.

FIG. 3B is a schematic diagram showing an integrated therapy pad beingtransferred between medical devices, in accordance with at least oneexample disclosed herein.

FIG. 3C is a schematic diagram showing a chest compression sensor beingtransferred between medical devices, in accordance with at least oneexample disclosed herein.

FIG. 3D is a schematic diagram showing an integrated therapy pad beingoverlaid on a chest compression sensor, in accordance with at least oneexample disclosed herein.

FIG. 4 is a schematic diagram showing a breathing assistance accessorybeing transferred between medical devices, in accordance with at leastone example disclosed herein.

FIG. 5A is a block diagram of a medical device accessory including anintegrated memory, in accordance with at least one example disclosedherein.

FIG. 5B is a schematic diagram showing the accessory of FIG. 5A operablycoupled to a computing device, in accordance with at least one exampledisclosed herein.

FIG. 5C is a block diagram of an alternative medical device accessoryincluding an integrated memory, in accordance with at least one exampledisclosed herein.

FIG. 6A is a block diagram of a medical device accessory including aremovable memory, in accordance with at least one example disclosedherein.

FIG. 6B is a block diagram of a medical device including the integratedmemory of FIG. 6A, in accordance with at least one example disclosedherein.

FIG. 6C is a schematic diagram showing the removable memory of FIG. 6Aoperably coupled to a computing device, in accordance with at least oneexample disclosed herein.

FIG. 7A is a flow diagram of illustrating a process of monitoring andrecording information to a medical device accessory-based memory, inaccordance with at least one example disclosed herein.

FIG. 7B is a more detailed flow diagram of the process of monitoring forrecording information to a medical device accessory-based memory, inaccordance with at least one example disclosed herein.

FIG. 7C is a flow diagram illustrating a process of transferringrecorded information from a medical device accessory-based memory, inaccordance with at least one example disclosed herein.

FIGS. 8A-8D are illustrative data structures showing data stored in amedical device accessory-based memory, in accordance with at least oneexample disclosed herein.

FIG. 8E shows sample waveform data stored in a medical deviceaccessory-based memory, in accordance with at least one exampledisclosed herein.

FIG. 9A is a user interface screen for controlling transfer ofinformation from a medical device accessory-based memory, in accordancewith at least one example disclosed herein.

FIG. 9B is a user interface screen for viewing information stored on amedical device accessory-based memory, in accordance with at least oneexample disclosed herein.

FIGS. 10A and 10B are schematic diagrams of sample chest compressionsensors, in accordance with at least one example disclosed herein.

FIG. 11A is a schematic diagram of a sample neo-natal chest compressionsensor including a band, in accordance with at least one exampledisclosed herein.

FIG. 11B is a schematic diagram of a sample neo-natal chest compressionsensor including opposing sensors, in accordance with at least oneexample disclosed herein.

FIGS. 12A-12C are schematic diagrams of alternate closure assemblies fora sample neo-natal chest compression sensor, in accordance with at leastone example disclosed herein.

FIG. 13A is a schematic diagram of an example medical system, inaccordance with at least one example disclosed herein.

FIG. 13B is an alternate schematic diagram of an example medical system,in accordance with at least one example disclosed herein.

FIG. 14 is a block diagram of an example medical system, in accordancewith at least one example disclosed herein.

FIG. 15 is a schematic diagram illustrating a medical device inaccordance with at least one example disclosed herein.

FIG. 16 is a schematic diagram illustrating another medical device inaccordance with at least one example disclosed herein.

DETAILED DESCRIPTION

Typically, when a cardiac patient experiences a cardiac event such as anarrhythmia, the quicker the patient is provided treatment the greaterthe chances of survival. As such, many public places are equipped withwall mounted or otherwise portable and readily available automaticexternal defibrillators (AEDs). A wall mounted AED may include adefibrillator device and an integrated therapy pad that includes sensingand treatment electrodes as well as a chest compression sensor. Ingeneral, the surface of the integrated therapy pads present printedinstructions describing where to position the pad on the patient's bodyand how to begin/administer treatment to the patient.

In most instances, unless the patient experiences the cardiac event inclose range to trained emergency responders, first responders to thepatient will typically be bystanders such as family or friends of thepatient or strangers who happen to be near the patient when the cardiacevent occurred. As such, treatment of the patient is generally begun bythe first responders prior to arrival of trained emergency respondersusing, for example, a wall mounted AED as described above.

In time, the trained emergency responders will arrive on the scene totreat the patient. The trained emergency responders will typically bringtheir own medical devices, such as a defibrillation device and/or anautomated ventilator. Often such devices used by trained responderscontain more advanced capabilities than the more basic medical device(s)(e.g. public access AEDs) more readily available to the firstresponder(s). Rather than using the more basic medical device(s) thatare first applied to the patient, the trained emergency responders willuse devices that typically have more advanced monitoring and treatmentcapabilities compared to the initial AED. However, rather than removingall of the equipment that has already been applied to the patient, suchas electrodes and chest compression sensor, depending upon themanufacturer and compatibility, for example, the trained emergencyresponders may be able to simply disconnect the existing equipment onthe victim from the initial AED and connect it directly to their, morefamiliar and possibly more advanced defibrillation device.

However, one potential problem with such an approach is that the trainedemergency responders may be uninformed about specific details of thesituation such as physiological information of the patient prior toarrival, timing information, what treatment information has already beenprovided to the patient, the patient's response to the treatment,whether the treatment was successful or not, responder actions duringtreatment, how well the responder performed certain actions such aschest compressions and/or ventilations, and other similar details. Thetime spent determining these details can further delay proper diagnosisand treatment of the patient.

Aspects of the present disclosure are designed to reduce or eliminateuncertainty on the parts of the trained emergency responders byproviding, for example, memory integrated into an accessory such as apatient-coupled resuscitation device that is configured to recordinformation about the patient prior to, during, and after treatment. Insuch an examples, the patient-coupled resuscitation device can act as astore of information related to the patient's care and treatment thatmigrates and transfers such information between devices. For instance,relevant medical information recorded by a first medical device may bestored directly on the patient-coupled resuscitation device or anothersimilar accessory, so that when the second (more advanced) medicaldevice arrives, the patient-coupled resuscitation device or anothersimilar accessory having all the relevant information stored thereon maybe decoupled from the first medical device and then coupled to thesecond medical device, so as to transfer the relevant information to thesecond medical device, immediately making such information readilyavailable to the trained emergency responder. This way, the trainedemergency responder no longer has to find the first medical device andretrieve the relevant medical information therefrom.

As an example, the integrated therapy pad as described above can bemodified to include a non-volatile memory as described herein that isconfigured to record various information such as patient physiologicalinformation (e.g., ECG waveforms, CO2 waveforms/information, oxygensaturation data, etc.), operational information for the AED duringtreatment, patient response to the treatment, patient characteristicdata, rescuer performance data (e.g., CPR performance), amongst otherrelevant medical information. Upon disconnection of the integratedtherapy pad from the initial AED and connection of the pad to thetrained emergency responders' defibrillation device (which may beconfigured to act as a patient monitor), the information stored on thememory can be automatically transferred to the defibrillation device,thereby updating the defibrillation device with all collected andavailable information. The defibrillation device can then immediatelycontinue the monitoring and/or treatment of the patient as was beingperformed by the initial AED.

As another use scenario, in a hospital setting, a patient may requireCPR in the form of chest compressions and/or ventilations, however, thedefibrillator/monitor may not always be readily available.Traditionally, chest compression feedback is provided with thedefibrillator/monitor, however this system that includes thedefibrillator/monitor is often later arriving, and so unfortunately,chest compressions are often provided without proper feedback. Hence, itmay be desirable for there to be a mechanism for providing chestcompression and/or ventilation feedback before the defibrillator/monitorarrives. Accordingly, a standalone chest compression monitoring deviceor sensor may be provided nearby a patient (e.g., in the room, at thebedside, on a wall or shelf, etc.), along with a bag-valve mask, so thatchest compressions and/or ventilations, with feedback, may be providedto the patient, despite the absence in the moment of adefibrillator/monitor. The standalone chest compression monitoringdevice may have non-volatile memory that is able to record and storepatient physiological data, patient characteristics data, and rescuerperformance data. When a later arriving defibrillator and/or monitoringmedical device arrives, the standalone chest compression monitoringdevice may be able to establish a communicative connection (e.g.,wireless or wired) with the medical device and, hence, provide the laterarriving medical device with all the relevant patient, treatment,rescuer performance, medical information that had been previouslyrecorded. The standalone chest compression device may provide feedbackfor a rescuer providing manual compressions to adjust the manner inwhich chest compressions are given. For example, the compression devicemay be able to provide, on the device itself and/or on a companioninterface (e.g., tablet screen, other display and/or speaker) anindication of the compression depth, rate, release velocity and/or otherparameter that the rescuer is applying, and whether or not thecompression parameter(s) are within desired target range(s).

Similarly the case with a bag-valve mask (BVM) with flow sensingcapabilities, which may be provided with non-volatile memory that isable to record and store patient physiological data, patientcharacteristics data, and rescuer performance data. When the laterarriving defibrillator and/or monitoring medical device arrives, theflow sensor device may be able to establish a communicative connection(e.g., wireless or wired) with the medical device and provide the laterarriving medical device with all the relevant patient, treatment,rescuer performance, medical information that had been previouslyrecorded. The BVM and/or flow sensor device may provide feedback for arescuer providing manual ventilations to adjust the manner in whichventilations are given. For example, the flow sensing device may be ableto provide, on the device itself and/or on a companion interface (e.g.,tablet screen, other display and/or speaker) an indication of the tidalvolume, ventilation rate, minute volume and/or other parameter that therescuer is applying, and whether or not the ventilation parameter(s) arewithin desired target range(s).

Thus, and in accordance with at least some of the examples as describedherein, resuscitation accessories such as patient-coupled resuscitationdevices for use with various medical devices having integrated memoryfor storing information about the operation of the medical devices aredescribed. In some examples, the resuscitation accessory optionallyincludes a sensor configured to acquire medical information, the medicalinformation comprising at least one of: patient physiological data,patient characteristic data, and rescuer performance data. The accessorycan further include a memory and at least one processor operably coupledto the memory and the sensor. The at least one processor can beconfigured to receive the medical treatment device information acquiredby the sensor during monitoring of a patient prior to and/or duringtreatment of the patient and record the medical treatment deviceinformation to the memory. In some examples, the processor is furtherconfigured to automatically transfer the medical treatment deviceinformation to another device upon connection of the accessory to thedevice. In some examples, the processor can be configured to respond toa request for a transfer of the medical treatment device information toanother device.

In some examples, patient-coupled resuscitation devices for use with aplurality of medical devices are described. In at least one example, apatient-coupled resuscitation device can include a patient-coupledportion configured to provide resuscitative treatment to the patient, aconnector configured to electrically connect the patient-coupledresuscitation device to at least one of a first medical device and asecond medical device, and a housing including a non-volatile memory andassociated circuitry. In some examples, the non-volatile memory andassociated circuitry can be configured to store a device identifierreadable by the first medical device and the second medical device toidentify the patient-coupled resuscitation device, receive medicaltreatment information from the first medical device via the connector,the medical treatment information comprising at least one of: patientphysiological data, patient characteristic data, and rescuer performancedata, receive timing information of the medical treatment informationfrom the first medical device via the connector, record the medicaltreatment information and the timing information, and transfer, upondetecting an electrical connection to the second medical device, themedical treatment information and the timing information to the secondmedical device.

In some examples, a patient-coupled resuscitation device can include adefibrillation electrode configured for use with a plurality ofdefibrillation devices. The electrode can include a memory, a connectorconfigured to operably couple the defibrillation electrode to one of theplurality of defibrillation devices, a skin contacting portionconfigured to contact skin of a patient, and at least one processoroperably coupled to the memory. The processor can be configured todetermine patient physiological data based upon signals collected by theskin contacting portion during monitoring of a patient prior to andduring treatment. The processor can also be configured to determinedevice operational data related to operation of the one of the pluralityof defibrillation devices operably coupled to the defibrillationelectrode prior to and during treatment. The processor can further beconfigured to record the patient physiological data and the deviceoperational data to the memory.

In some examples, additional patient-coupled resuscitation devices foruse with a plurality of medical devices are described. An additionalpatient-coupled resuscitation device can include a patient-coupledportion configured to provide resuscitative treatment to the patient anda housing including a wireless communications interface and associatedcircuitry and a non-volatile memory and associated circuitry. In someexamples, the wireless communications interface and associated circuitrycan be configured to detect and establish a short-range wirelessconnection with a first medical device, and detect and establish, at asubsequent time, a short-range wireless connection with a second medicaldevice. In some examples, the non-volatile memory and associatedcircuitry can be configured to store a device identifier readable by thefirst medical device and the second medical device to identify thepatient-coupled resuscitation device, receive and record, upon theshort-range wireless connection with the first medical device beingestablished, medical treatment information from the first medicaldevice, the medical treatment information comprising at least one ofpatient physiological data, patient characteristic data, and rescuerperformance data, and transfer, upon detecting the short-range wirelessconnection with the second medical device, the medical treatmentinformation to the second medical device.

In some examples, medical treatment devices for managing medicaltreatment information are described. A medical treatment device caninclude at least one sensor configured to obtain medical data, a batterycomprising a non-volatile memory and associated circuitry configured tostore medical device information, a receptacle to which the battery isremovably coupled and configured to draw power from the battery, and atleast one processor coupled to the at least one sensor and the battery.The at least one processor can be configured to receive the medical datafrom the at least one sensor, process the medical data to generatemedical treatment information, the medical treatment informationcomprising at least one of: patient physiological data, patientcharacteristic data, and rescuer performance data, and record themedical treatment information to the non-volatile memory of the battery.

In some examples, systems for assisting in medical treatment of apatient and for managing medical treatment information are described. Anexample system can include a patient-coupled resuscitation devicecomprising a non-volatile memory and associated circuitry configured tostore a device identifier readable by a plurality of medical devices toidentify the patient-coupled resuscitation device and record medicaltreatment information comprising at least one of patient physiologicaldata, patient characteristic data, and rescuer performance data, and afirst medical device comprising at least one first processor configuredto receive and record the medical treatment information comprising atleast one of: patient physiological data, patient characteristic data,and rescuer performance data, establish a first communicative connectionwith the patient-coupled resuscitation device, and transfer the medicaltreatment information to the patient-coupled resuscitation device viathe first communicative connection. The example system can furtherinclude a second medical device comprising at least one second processorconfigured to establish a second communicative connection with thepatient-coupled resuscitation device, and receive and record the medicaltreatment information from the patient-coupled resuscitation device viathe second communicative connection.

In some situations as described herein, a medical device accessory suchas a patient-coupled resuscitation device can include a chestcompression sensor. However, a typical chest compression sensor can beinappropriate for use in some scenarios. For example, when treating aneo-natal patient, a typical chest compression sensor may be too big toproperly be positioned on and monitor such a small patient.Additionally, with a newborn patient, the baby is typically covered influid that may make positioning and securing a chest compression sensordifficult. As time is a factor in saving a patient, cleaning the baby istypically unfeasible.

Aspects of the present disclosure are designed to provide a chestcompression sensor that is adapted to or suitable for use with aneonatal patient. For example, as described herein, a chest compressionsensor can include an elastic strap that is configured to be positionedabout the patient's torso, thereby holding the chest compression sensorin proper position during treatment such as cardiopulmonaryresuscitation (CPR). In some examples, the strap can include anadjustable closure such as a ratchet or buckle that provides for anadjustable fit about the torso of the patient, increasing thereliability of information collected by the chest compression sensor.

Example Medical Devices

As noted above, a medical device can be configured to record informationrelated to treatment of the patient for later review and analysis. Insome examples, the medical device can be configured to record thisinformation onto a removable storage device such as memory integratedinto a removable battery. Information related to the operation of themedical device as well as information obtained from or related to theoperation of any accessories connected to or otherwise associated withthe medical device can be recorded onto the memory. For example, asshown in FIG. 1 , a medical device such as defibrillator 102 can includea removable battery 104 that is configured to provide power to thedefibrillator as well as to record information about operation of thedefibrillator as described herein.

As further shown in FIG. 1 , the defibrillator 102 can be configured tooperate with various resuscitation accessories. For example, thedefibrillator 102 can include an electrical connector that is configuredto operably couple to one or more accessories such as integrated therapypad 106 including a combination set of electrodes/chest compressionsensor, a set of standalone monitoring/treatment electrodes 108. Thedefibrillator can also be configured to couple to a bag-valve-mask (BVM)110 including, for example, a ventilation bag, which is connected to aventilation valve and a mask, as well as an integrated flow sensor. Insome examples, the defibrillator 102 can be further configured to coupleto a standalone chest compression sensor 112 that has functionality toprovide chest compression feedback without requiring the defibrillator.In certain implementations, the defibrillator 102 can be configured tocouple to the chest compression sensor 112 via a wired or wirelessconnection.

Depending upon which patient-coupled resuscitation device or accessoryis coupled to the defibrillator 102, the defibrillator can be configuredto perform one or more operations and to record specific informationrelated to the one or more operations to the removable memory includedin battery 104. For example, if the integrated therapy pad 106 iscoupled to the defibrillator 102, the defibrillator can receiveelectrical signals measured by, for example, one or more sensingelectrodes integrated into the therapy pad. The defibrillator 102 cananalyze the electrical signals to determine one or more physiologicalsignals for the patient. For example, the one or more physiologicalsignals can include heart rate metrics, RR interval metrics, heart ratevariability metrics, premature ventricular complex burden or counts,atrial fibrillation burden metrics, pauses, heart rate turbulencemetrics, QRS height, QRS width, changes in a size or shape of morphologyof the received ECG information, cosine R-T, artificial pacing, QTinterval, QT variability, T wave width, T wave alternans, T-wavevariability, and/or ST segment changes. The defibrillator 102 canfurther analyze the one or more physiological signals to determine ifthe patient is experiencing a cardiac event such as an arrhythmia anddetermine whether to provide treatment such as one or moredefibrillation shocks to the patient based upon the analysis.

Similarly, the defibrillator 102 can collect information from otheraccessories that are operably coupled to the defibrillator and store theinformation in the memory of the accessories. For example, the BVM 110is coupled to the defibrillator 102, so the defibrillator can determineand record various information from the flow rate sensor such asrespiratory rate metrics, inhaled oxygen level information, end-tidalCO2 information, and other similar metrics. In another example, thechest compression sensor 112 is coupled to the defibrillator 102, so thedefibrillator can determine and record various information such as chestcompression rate information, chest compression depth information, andother similar metrics.

It should be noted that a portable external defibrillator is shown inFIG. 1 by way of example. In certain implementations, a wearablecardio-defibrillator such as a WCD such as the LifeVest® WearableCardioverter Defibrillator from ZOLL Medical Corporation (Chelmsford,MA) can be provided as the medical device as described herein.

In another example, as shown in FIG. 2 , a medical device such asventilator 202 can include a removable battery 204 that is configured toprovide power to the ventilator as well as to record information aboutoperation of the ventilator as described herein.

As further shown in FIG. 2 , the ventilator 202 can be configured tooperate with various resuscitation accessories. For example, theventilator 202 can include an electrical connector that is configured tooperably couple to one or more accessories such as a chest compressionsensor 206, a BVM 208 including, for example, an integrated flow sensor,and breathing assistance device 210 including an endotracheal tube forpatient intubation. Depending upon which patient-coupled resuscitationdevice or accessory is coupled to the ventilator 202, the ventilator canbe configured to perform one or more operations and to record specificinformation related to the operation of the removable memory included inbattery 204 in this example. For example, if the chest compressionsensor 206 is coupled to the ventilator 202, the ventilator candetermine and record various information such as chest compression rateinformation, chest compression depth information, and other similarmetrics. If the BVM 208 of the breathing assistance device 210 iscoupled to the ventilator 202, the ventilator can determine and recordvarious information from the flow rate sensor such as respiratory ratemetrics, inhaled oxygen level information, end-tidal CO2 information(for systems that integrate CO2 sensing), ventilation tidal volume,ventilation rate, minute volume, and other similar respiration metrics.

In certain situations, treatment of a patient can transition from afirst treatment device to a second treatment device. For example, apatient experiencing a cardiac event such as an arrhythmia may first betreated using a publicly available AED mounted on, for example, a wallof an airport. The person administering the initial treatment may be apasserby, a family member or friend of the patient, or another similarperson with limited training in using the treatment device. After aperiod of time, additional people such as emergency medical respondersmay arrive at the scene and take over treatment of the patient. In sucha situation, the emergency medical responders will likely bring moreadvanced medical treatment devices, such as a defibrillator/monitor withtreatment capabilities or a patient monitor with monitoringfunctionality but absent the ability to provide treatment, and willtransition treatment of the patient to those devices. In such anexample, transferring any information about the patient and thetreatment of the patient to the new treatment device can beadvantageous. Accordingly, a patient-coupled resuscitation device and/orother accessory such as those described herein may be equipped withprocessing and/or memory that enables any and all relevant patientinformation to be recorded thereon from the first medical device, andthen transferred to the second medical device. This allows for a morecomplete, integrated patient care record that includes deviceidentification and/or usage information, along with the associatedpatient physiological and treatment information.

The more complete patient care record, including medical treatmentinformation (e.g., patient physiological data, patient characteristics,rescuer performance data) recorded from both the first medical deviceand the second medical device may then be available for post-case reviewby other medical personnel who were not present at the scene, withouthaving to collect the data gathered from each device separately, andthen having to merge or consolidate the information together. Forexample, since data gathered by the first medical device is recordedonto and transferred to the second medical device or other computingdevice via the accessory, the post-case review personnel may be able toview what the patient's presenting ECG rhythm was during the time whenthe first defibrillation shock(s) were given and also whether CPR (e.g.,chest compressions and/or ventilations) was provided to the patient and,if so, further view the overall quality of the CPR, before more highlytrained personnel were able to arrive at the scene. The post-case reviewpersonnel are also able to view any and all relevant informationrecorded by the more advanced second medical device as well, and be ableto determine from which medical device the information originated.

For example, as shown in FIG. 3A, a patient can be initially treated byan AED 302 powered by battery 304. The AED 302 can be configured torecord information related to the patient as well as treatment specificinformation onto a memory integrated into battery 304 as describedabove. In certain implementations, the memory can be integrated into aconnector of the battery.

In certain implementations, the AED 302 can monitor patient electricalsignals received from the integrated therapy pad 306 and record anypatient physiological information determined from the electrical signalsto the battery 304. Similarly, the AED can receive information relatedto any chest compressions applied to the patient from an integratedchest compression sensor included in the integrated therapy pad 306. Ifthe AED 302 delivers one or more defibrillation and/or pacing shocks tothe patient, the AED can record information related to the treatment tothe battery 304 as well. For example, the information can include energydelivered to the patient in the shock as well as whether the shocksuccessfully returned the patient to a normal cardiac rhythm.

In certain implementations, the battery 304 can be configured to storeadditional information related to the battery itself. For example, theinformation can include information such as the battery serial number(as assigned, for example, by the battery manufacturer or a medicaldevice manufacturer), remaining capacity information, number of highenergy charges, information related to AED functionality (e.g.,self-test results, calibration information, electrode padstatus/expiration) and other similar battery information. Additionalexamples of battery information is described below in the discussion ofFIG. 8D. When the battery 304 is inserted into a device such as AED 302,the AED can create a battery information file as well that includesinformation about the battery being used for later reference. Forexample, the AED battery information file can include batteryidentification information, battery usage information, current batterystatus information, and other similar battery information. This AEDbattery file provides a data structure that can be retrieved to gethistorical usage information for batteries that have been inserted intoa particular medical device such as an AED

A specific battery software task can be configured to, when executed,cause a processor to read/write battery data to both the battery memoryas described herein as well as to the memory of the AED (or othermedical device being powered by the battery). The battery software taskcan be configured to write additional information such as installationdate, self-test information, battery verification information, and anyerrors associated with the battery. During a self-test, the batterysoftware task can confirm the battery manufacture date, confirm thecurrent date, calculate the battery life consumed, calculate a batteryremaining charge, log any errors, check for battery expiration, checkthe battery voltage, and update a display of the AED to include variousinformation such as battery capacity and a battery expiration date. Uponcompletion of the self-test, the battery software task can be configuredto update the battery consumed charge over time, wait for eventsindicating that the AED capacitor is charged and update the consumedcharge accordingly, and update the AED display with remaining batterycapacity information. However, it should be noted that the batterysoftware task as described herein is provided by way of example only.Depending upon system design, the functionality of the battery softwaretask as described herein can be divided among multiple more focusedsoftware tasks.

Referring again to FIGS. 3A-3D, upon arrival of emergency medicalresponders, treatment of the patient can be transferred to the moreadvanced defibrillator/monitor 310. In this example, the battery 304 canbe removed from AED 302 and inserted into defibrillator/monitor 310.Upon insertion, the defibrillator/monitor 310 can access any informationstored in the memory of battery 304 and can resume treatment of thepatient based upon the information already collected by the AED 302. Forexample, if a defibrillation shock delivered by the AED 302 wasunsuccessful, the defibrillator/monitor 310 can deliver a subsequentdefibrillation shock to the patient using integrated therapy pad 312.

It should be noted that two integrated therapy pads 306 and 312 areshown by way of example only in FIG. 3A. In certain implementations, theintegrated therapy pad 306 can be disconnected from the AED 302 andcoupled to the defibrillator/monitor 310. For example, as shown in FIG.3B, an integrated therapy pad can be disconnected from a first medicaldevice and coupled to a second medical device while remaining in placeon the patient.

More specifically, as shown in FIG. 3B, a medical device such asdefibrillator 320 can be operably coupled to an integrated therapy pad325 that includes, for example, a set of sensing and treatmentelectrodes as well as a chest compression sensor. A set of firstresponders can initially place the integrated therapy pad 325 onto apatient that is experiencing, for example, a cardiac event such as anarrhythmia. The defibrillator 320 can monitor and, if necessary, providetreatment to the patient via the integrated therapy pad 325, and whiledoing so, may record relevant patient and medical information, such aspatient physiological data, patient characteristics, rescuer performancedata, etc., to the integrated therapy pad 325. At a time when a secondset of responders such as trained emergency medical responders arrive,it may be necessary to transfer monitoring and treatment of the patientto a second medical device. As shown in FIG. 3B, the second medicaltreatment device can be a second defibrillator 330. In this example, theemergency medical responders can disconnect the integrated therapy pad325 from the first defibrillator 320 and couple the integrated therapypad to the second defibrillator 330. By doing so, the data recorded bythe first defibrillator 320 and written to the non-volatile memory ofthe integrated therapy pad 325 may be written to the seconddefibrillator 330, so that all the relevant patient case information isavailable together.

In certain implementations, a patient-coupled resuscitation device orother similar medical device accessory such as the integrated therapypad 325 as shown in FIG. 3B can include an integrated memory that isconfigured to store information, similar to battery 304 as describedabove in regard to FIG. 3A. For example, the integrated memory in theaccessory can be configured to store information about the patient suchas measured physiological information. In some examples, the integratedmemory in the accessory can be configured to store information about anytreatments that have been delivered to the patient. For example, if thefirst defibrillator 320 has delivered one or more defibrillation shocksto the patient, information about the defibrillation shock can be storedon the memory in the integrated therapy pad 325. Then, when theintegrated therapy pad 325 is coupled to the second defibrillator 330,the information about the patient and any potential treatmentinformation stored on the memory can be transferred to the seconddefibrillator 330. The second defibrillator 330 can then continuetreatment of the patient using the patient information and treatmentinformation stored on the memory in the integrated therapy pads 325.Additional information about integrated memory in medical deviceaccessories is provided in the discussion of FIGS. 5-6C below.

In certain implementations, additional accessories can be disconnectedfrom a first medical device and operably coupled to a second medicaldevice as described herein. For example, as shown in FIG. 3C, a medicaldevice such as a first defibrillator 340 can be operably coupled to achest compression sensor 345. Depending upon the capabilities of thefirst defibrillator 340 and the chest compression sensor 345, a wired orwireless connection can be established. For example, the firstdefibrillator 340 and the chest compression sensor 345 can be configuredto establish a wireless connection using a short-range communicationscheme such as Bluetooth® or a near field communication (NFC) protocol.

A set of first responders can initially place the chest compressionsensor 345 onto a patient that is experiencing, for example, a cardiacevent such as an arrhythmia. If the first responders administer CPRtreatment to the patient, the chest compression sensor 345 can monitorand record various information related to the treatment such as averagecompression rate, average compression depth, maximum compression depth,minimum compression depth, elapsed time of treatment administered,release velocity, and other relevant information. The firstdefibrillator 340 can monitor and, if necessary, present feedback to thefirst responders via an integrated display on the device. At a time whena second set of responders such as trained emergency medical respondersarrive, it may be necessary to transfer monitoring and treatment of thepatient to a second medical device. As shown in FIG. 3 c , the secondmedical treatment device can be a second defibrillator 350. In thisexample, the emergency medical responders can disconnect the chestcompression sensor 345 from the first defibrillator 340 and couple thechest compression sensor 345 to the second defibrillator 350. If thereis a wired interface between the first defibrillator 340 and the chestcompression sensor 345, this can include disconnecting the chestcompression sensor 345 from the first defibrillator and connecting thechest compression sensor 345 to the second defibrillator. If there is awireless connection between the first defibrillator 340 and the chestcompression sensor 345, the emergency medical responders can physicallymove the first defibrillator away from the chest compression sensor 345(e.g., more than ten feet away) and place the second defibrillator 350into closer proximity to the chest compression sensor 345 (e.g., withinthree to five feet in case of a proximity based detection). The chestcompression sensor 345 and the second defibrillator 350 can beconfigured to automatically establish a wireless connection upon beingbrought into proximity of one another. In some examples, one or both ofthe chest compression sensor 345 and one or both of defibrillators 340and 350 can have a manual connection button that, upon activation (e.g.,being pressed by a medical responder) will initiate a wirelessconnection protocol.

For example, a patient-coupled resuscitation device or other similaraccessory and an external medical device can be configured tocommunicate using a specific wireless connection protocol such asBluetooth, Zigbee, near-field communications, infrared, and othersimilar protocols. In certain implementations, if the accessory isconfigured to communicate with a medical device using Bluetooth, theaccessory can be configured to monitor a specific frequency such as 2.45GHz for a Bluetooth broadcast signal being issued by the medical device.Based upon the type of Bluetooth being used, the broadcast signal mayonly be detectable within a specific radius of the medical device (e.g.,within 30 feet). When positioned within that radius, the accessory andthe medical device may exchange authentication information and begin tocommunicate wirelessly. In another example, the accessory and themedical device can be configured to communicate using anothercommunication protocol such as Zigbee. In such an example, the accessorycan monitor a specific frequency such as 2.4 GHz for a Zigbee broadcastsignal being issued by the medical device. Upon receiving the broadcastsignal, the accessory and the medical device can exchange authenticationinformation and communicate using the Zigbee protocol.

It should be noted that the specific communication protocols and signalfrequencies as described above are by way of example only. In certainexamples, the accessory can be configured to monitor additionalfrequency ranges for broadcast communication signals. For example, theaccessory can be configured to monitor signals around 850-950 MHz,2.2-2.6 GHz, 4.75-5.25 GHz, 5.8-6.0 GHz, and other similar frequencies.Similarly, a 30 foot radius in which a broadcast signal is detectable asnoted above is provided by way of example only. In certain examples, awireless communication broadcast radius can include 1-2 feet, 2-5 feet,5-10 feet, 10-25 feet, and 25-50 feet. It should also be noted that themedical device is described as transmitting the broadcast signal aboveby way of example only. In some implementations, the accessory can beconfigured to transmit a wireless communication protocol broadcastsignal for detection by one or more medical devices.

Similar to the above discussion of FIG. 3B, the chest compression sensor345 can include an integrated non-volatile memory that can be configuredto store information about the patient as well as patient treatmentinformation including, for example, average compression rate, averagecompression depth, maximum compression depth, minimum compression depth,release velocity, elapsed time of treatment administered, and othersimilar information. When the chest compression sensor 345 is coupled tothe second defibrillator 350, the information about the patient and anypotential treatment information stored on the memory can be transferredto the second defibrillator 350. The second defibrillator 350 can thencontinue monitoring treatment of the patient using the patientinformation and treatment information stored on the memory in the chestcompression sensor 345 as reference for informing future monitoring andtreatment.

In addition to transferring information between medical devices, thetechniques and processes as described herein can be used to transferinformation between medical device accessories as well. For example, asshown in FIG. 3D, a medical device such as a defibrillator 360 can beoperably coupled to a patient-coupled resuscitation device or othersimilar medical device accessory such as chest compression sensor 365.Initial treatment such as CPR can be administered to a patient.Information about the treatment can be recorded by both thedefibrillator 360 and the chest compression sensor 365. For example, thechest compression sensor can be configured to monitor and record variousinformation such as average compression rate, average compression depth,maximum compression depth, minimum compression depth, release velocity,CPR fraction (e.g., percentage of time that CPR is actually being givento the patient during periods designated for CPR), percentage ofcompression depth and rate that are within target ranges, elapsed timeof treatment administered, and other similar information. At some point,another accessory can be operably coupled to the defibrillator 360. Forexample, as shown in FIG. 3D, an integrated therapy pad 370 can beoverlaid onto the chest compression sensor 365. The integrated therapypad 370 can be coupled to the defibrillator 360 and begin monitoring thepatient and, if necessary, provide treatment such as a defibrillationshock to the patient. In certain implementations, upon placement overthe chest compression sensor 365, the integrated therapy pad 370 candownload or otherwise access the information stored on the chestcompression sensor. For example, the integrated therapy pad 370 can beconfigured to establish a wireless connection with the chest compressionsensor 365 using a short-range communication protocol such asBluetooth®. Upon establishing a connection, the integrated therapy pad370 can access and download the information stored on the memory in thechest compression sensor.

In addition to transferring a patient-coupled resuscitation deviceand/or other medical device accessory between two medical devices of thesame or a similar functionality, a medical device accessory can betransferred between two medical devices that have different overallfunctionalities. For example, a medical device accessory such as abreathing assistance accessory including a flow sensor can betransferred between a defibrillator and a ventilator. As shown in FIG. 4, during initial patient treatment, a patient-coupled resuscitationdevice such as breathing assistance accessory 405 can be initiallycoupled to a defibrillator 400. As shown in FIG. 4 , the breathingassistance accessory 405 can include a bag valve mask and flow sensorassembly 406 that includes, for example, a flow sensor configured tomeasure air flow. The breathing assistance accessory 405 can furtherinclude a mask 407 for placement over the patient's mouth and a bag 408that can be used by a medical responder to pump air into the patient'slungs.

As further shown in FIG. 4 , the breathing assistance accessory 405 canbe disconnected from the defibrillator 400 and operably coupled to anautomatic ventilator 410. Additionally, upon transferring to theautomatic ventilator 410, the mask 407 portion of the breathingassistance accessory 405 can be removed, and the valve and sensorassembly 406 can be attached to an endotracheal tube 409 that has beenintegrated into the patient's airway for automatic ventilation.Depending upon the design of the breathing assistance accessory 405, thebag 408 can also be removed.

Similar to above, when coupled to the defibrillator 400, an integratedmemory in the breathing assistance accessory 405 can be storinginformation measured by the flow sensor. For example, the memory canstore information related to rate of air flow, volume of air flow,ventilation tidal volume, minute volume, ventilation rate, percentage oftidal volume or ventilation rate that are within desired target ranges,and other similar air flow information. When disconnected from thedefibrillator 400 and coupled to the ventilator 410, the informationstored on the memory in the breathing assistance accessory 405 can betransferred to the ventilator as described herein. In certainsituations, the resuscitation accessory may be able to record theparticular medical device identification to memory, for the benefit ofthe second medical device or computing device. The second medical deviceor other computing device may then be able to initiate a network and/orproximity search for the first medical device and establish acommunicative connection to exchange relevant medical informationwithout further requiring the accessory.

As an example use scenario, an initial emergency service or responderarrives and monitors the patient using a first defibrillator/monitorequipped with various accessories, such as electrodes and a chestcompression sensor in accordance with the present disclosure. The firstdefibrillator/monitor connected to those accessories records its uniquesignature or serial number thereto. When another, similar or possiblymore advanced, second medical device arrives on the scene, theaccessory(ies) are disconnected from the first defibrillator/monitor andconnected to the second medical device. The second medical device readsthe signature of the first defibrillator/monitor from the accessory, andthen initiates a network or proximity search for the particular devicewith the unique signature. Once that device (firstdefibrillator/monitor) is discovered, then a communicative connectionmay be established so as to transfer relevant medical informationimmediately.

In another example, if an ambulance service is transferring a patient toa hospital, a patient-coupled resuscitation device or other similaraccessory disconnected from a first medical device associated with theambulance service and subsequently connected to a second medical deviceassociated with the hospital would have recorded thereon the signaturecorresponding to the first medical device associated with the ambulanceservice. Once the second medical device associated with the hospitalreads that there is an identification signature recorded on theresuscitation accessory, the second medical device may initiate anetwork or proximity search for the first medical device (in this case,the ambulance service may remain nearby and/or stay on the same networkso as to be available) and establish a communicative connection toinitiate the transfer of relevant medical information. For example, thedevices may establish communication via a near field communication(NFC), Bluetooth, WiFi, or other suitable manner, and then initiate datatransfer directly, without further requiring the accessory.

In the event that the disconnecting medical device is not maintained inclose proximity to the new connecting medical device for a complete datatransfer, the device identification signature may still be stored withthe record on the newer medical device such that whenever the previousmedical device establishes a link back to a wireless/wired connection,the two medical devices may then connect with one another to initiateand/or complete data transfer.

Integrated and Removable Memory in Medical Device Accessories

As noted above, a patient-coupled resuscitation device and medicaldevice accessories such as an integrated therapy pad, a chestcompression sensor, a breathing assistance accessory such as a BVM, aset of defibrillation electrodes, a battery for powering one or moremedical devices, and other similar medical device accessories caninclude an integrated memory configured to store various information asdescribed herein. For example, as shown in FIG. 5A, a medical deviceaccessory 500 can include various components configured to facilitatecollection and storage of information related to operation of themedical device accessory and treatment provided to a patient. As shownin FIG. 5A, the accessory 500 can include a processor 502, one or moresensors 504, a user interface 506, a memory 508, an input/output (I/O)interface 510, and a timer 512. In some examples, the memory 508 usedmay employ a serial data interface to reduce pincount on connectorsbetween the accessory and the medical device particularly when thememory 508 is configured to be removable as shown in FIG. 6A. Forinstance, the memory 508 may be the AT24CM02 2 Mb I2C compatible 2-wireSerial EEPROM (MicroChip Inc.) Alternatively, the pincount may befurther reduced by using the 2 wire AT21CS01 2 lead with the clock, dataand power combined into a single input.

In some implementations, the processor 502 includes one or moreprocessors (or one or more processor cores) that each are configured toperform a series of instructions that result in manipulated data and/orcontrol the operation of the other components of the accessory 500. Asreferred to herein, the processor 502 can be configured to execute afunction where software is stored in a data store (e.g., memory 508)coupled to the processor, the software being configured to cause theprocessor to proceed through a sequence of various logic decisions thatresult in the function being executed. The various components that aredescribed herein as being executable by the processor 502 can beimplemented in various forms of specialized hardware, software, or acombination thereof. For example, the processor 502 can be a digitalsignal processor (DSP) such as a 24-bit DSP. The processor 502 can be amulti-core processor, e.g., having two or more processing cores. Theprocessor 502 can be an Advanced RISC Machine (ARM) processor such as a32-bit ARM processor or a 64-bit ARM processor. The processor 502 canexecute an embedded operating system, and include services provided bythe operating system that can be used for various functions performed bythe accessory 500.

As further shown in FIG. 5A, the one or more sensors 504 can be operablycoupled to the processor 502 and configured to provide information tothe processor. Depending upon the functionality of accessory 500, thesensors 504 can vary. For example, if the accessory is a chestcompression sensor, the sensors 504 can include one or moreaccelerometers configured to measure chest compression information suchas chest compression depth. In another example, if the accessory 500 isa breathing assistance accessory, the sensors 504 can include a flowsensor configured to measure air rate and volume information. Otherexamples of sensors can include ECG sensing electrodes, vibrationalsensors, acoustic sensors, tissue fluid monitors, and other types ofmotion sensors such as gyroscopes and magnetometers.

As also shown in FIG. 5A, the user interface 506 can be operably coupledto the processor 502. It should be noted that, depending upon thefunctionality and design of the accessory 500, a user interface may notbe included. However, in this example, the accessory includes a userinterface 506 that can include one or more physical interface devicessuch as input devices, output devices, and combination input/outputdevices and a software stack configured to drive operation of thedevices. These user interface 506 can be configured to can rendervisual, audio, and/or tactile content. Thus, the user interface 506 canreceive input or provide output, thereby enabling a user to interactwith the accessory 500.

As further shown in FIG. 5A, the memory 508 can be operably coupled tothe processor 502. The memory 508 can include one or more ofnon-transitory computer-readable media, such as flash memory, solidstate memory, magnetic memory, optical memory, cache memory,combinations thereof, and others. The memory 508 can be configured tostore executable instructions and data used for operation of theaccessory 500. In certain examples, the memory 508 can includeexecutable instructions that, when executed, are configured to cause theprocessor 502 to perform one or more operations. In some examples, thememory 508 can be configured to store information received from, forexample, the processor 502 and/or the sensors 504.

Additionally, as shown in FIG. 5A, the I/O interface 510 can be operablycoupled to the processor 502. The I/O interface can facilitate thecommunication of information between the accessory 500 and one or moreother devices or entities. For example, the I/O interface 510 can beconfigured to establish a communication link and facilitate transfer ofinformation stored in memory 508 to another medical device accessory, amedical device, a computing device associated with a healthcare provideror other similar person providing treatment to a patient, and othersimilar computing devices. For the information stored in memory 508 tobe maintained during transition between when it is unplugged from afirst device and when the stored information is accessed again, thememory 508 should be non-volatile, e.g. FLASH, EEPROM, battery-backedstatic memory, etc.

In certain implementations, the I/O interface can be configured toprovide a wired or wireless connection. For example, the I/O interfacecan include a physical electrical connector such as a universal serialbus (USB) port that is configured to provide a wired connection withanother computing device for the transfer of information. In someexamples, the I/O interface 510 can include communications circuitry fortransmitting data in accordance with a Bluetooth® wireless standard forexchanging such data over short distances to an intermediary device. Forexample, such an intermediary device can be configured as a medicaldevice, another medical device accessory, a smartphone, a tablet, aportable computing device, and/or other devices in proximity of theaccessory 500. The intermediary device(s) may in turn communicate thedata to a remote server over a broadband cellular network communicationslink. The communications link may implement broadband cellulartechnology (e.g., 2.5G, 2.75G, 3G, 4G, 5G cellular standards) and/orLong-Term Evolution (LTE) technology or GSM/EDGE and UMTS/HSPAtechnologies for high-speed wireless communication. In someimplementations, the intermediary device(s) may communicate with aremote server over a Wi-Fi™ communications link based on the IEEE 802.11standard.

As further shown in FIG. 5A, the timer 512 can be configured to recordtiming information related to operation of the accessory 500 and theinteraction of the accessory with an external medical device. Forexample, in certain implementations, the internal timer of the externalmedical device and the timer 512 may not be synchronized. In such anexample, the timer 512 can be configured to record timing information tomemory 508 that provides additional information related to the operationof the accessory 500 in concert with the external medical device. Insome examples, the timer 512 can be synchronized to the time of theexternal medical device. In other examples, the timer 512 can continueits original timing while adding a marker or other similar indication toa recorded timing information to provide an offset or synchronizationpoint for aligning timing information with the external medical device.

In some examples, the accessory 500 connected to the first externalmedical device may record timing information (e.g., clock time) of thefirst external medical device prior to being disconnected. When theaccessory 500 is disconnected from a first external medical device, thetimer 512 of the accessory 500 may continue to keep time as if theaccessory 500 remained connected with the first external medical device.And then when the accessory 500, which has maintained the timing of thefirst external medical device, is connected to a second external medicaldevice, any difference in time between the first and second externalmedical devices may be noted, or otherwise corrected for. As an example,when disconnected, the timer 512 can record timing information to thememory 508 indicating the clock time of the first medical device andwhen the accessory 500 was disconnected. When the accessory is connectedto a second external medical device, the second external device caninclude a different internal time as compared to one or both of thefirst external medical device and the accessory 500. In such an example,the recorded timing information as stored on memory 508 can be used tosynchronize the second medical device timer to the timer of the firstmedical device. In some examples, the recorded timing information onmemory 508 can be used to offset or otherwise adjust timing informationas recorded by the second external medical device to provide asynchronized and ordered recording of all treatment events measured bythe accessory 500 as administered by both the first external medicaldevice and the second external medical device. Or, when the accessory isconnected to the second medical device, the timing difference betweenthe first medical device and the second medical device may simply benoted.

In certain implementations, the accessory 500 can be configured tomonitor and provide treatment to a patient as described herein. In suchan example, the processor 502 can be configured to store information onthe memory 508 about the patient and any treatment provided to thepatient. For example, the processor 502 can be configured to storeinformation measured by the sensors 504 to the memory. Additionally, theprocessor 502 can be configured to store information related to thepatient that may be entered on the user interface 506 or otherwisereceived from an external device such as a medical device that theaccessory 500 is connected to. In some examples, the processor 502 canbe configured to store information related to any treatment provided tothe patient on the memory 508. The treatment information can be basedupon measured information from the sensors (e.g., chest compressioninformation that is indicative of CPR treatment being performed) orinformation received from a medical device such as defibrillation shockinformation.

As shown in FIG. 5B, information stored on the accessory 500 can betransferred to another device such as computing device 520. For example,the computing device 520 can be a computer associated with a patient'sphysician. Following treatment, the physician may want to review thepatient's information as stored on the accessory 500. The computingdevice 520 can establish a connection to the accessory 500 via the I/Ointerface. For example, as shown in FIG. 5B, the computing device 520can establish a wireless connection 522 and/or a wired connection 524with the accessory 500. The physician can then access the informationstored on the accessory 500 via, for example, a user interface similarto those as described below in the description of FIGS. 9A and 9B.

It should be noted that components shown as integrated into accessory500 in FIGS. 5A and 5B and described above are provided by way ofexample only. In some implementations, the accessory can include areduced set of components as compared to that shown in FIG. 5A. Forexample, in certain implementations, a sample accessory 550 can includea reduced set of components such as those shown in FIG. 5C. For example,accessory 550 can include processor 502, memory 508, and timer 512. Insuch an example, the accessory 550 can be configured to record timinginformation as described above as well as information received from anexternal medical device. Depending upon the type of patient-coupledresuscitation device or other similar accessory and the problems theaccessory addresses, a combination of components between those includedin FIG. 5A and those included in FIG. 5C can be included. For example, apatient-coupled resuscitation device or other similar accessory caninclude a processor, one or more sensors, a memory, and a timer. In someexamples, a patient-coupled resuscitation device or other similaraccessory as described herein can include a processor, one or moresensors, a memory, an I/O interface, and a timer. As such, the accessorydiagrams as shown in FIGS. 5A and 5C are merely provided by way ofexample only.

In addition to having an integrated memory as described herein, apatient-coupled resuscitation device or other similar accessory caninclude a removable memory. For example, as shown in FIG. 6A, anaccessory 600 can include a processor 602, one or more sensors 604, auser interface 606, an I/O interface 608, and a timer 614. Thesecomponents can be operably coupled and configured to function in acorresponding manner to similarly named components as shown in FIG. 5Aand described above. However, as further shown in FIG. 6A, the memory610 can be included in a removable module that is configured to bedetached or otherwise removed from the accessory 600. For example, theremovable memory 610 can be operably coupled to the other components ofthe accessory 600 via a memory connector 612. The memory connector 612can be configured to removably receive the removable memory 610 and toestablish an electrical connection between the removable memory and theother circuit components of the accessory 600 (e.g., processor 602,sensors 604, user interface 606, and I/O interface 608). In certainimplementations, the I/O interface 608 can be configured to communicatedirectly with the removable memory 610 via the memory connector 612 andact as an intermediary between the removable memory 610 and the othercircuit components of the accessory 600. In some examples, timer 614 canbe configured to record timing information as described above to theremovable memory 610.

In certain examples, the removable memory 610 can be implemented as acommercially available portable memory device such as a USB memorydevice, a secure digital (SD) memory device, and other similar portablestorage devices. The removable memory 610 can be housed within theaccessory 600 in a protected area that is not exposed to any potentialbody fluids or other debris that can result from treatment of a patient.As such, accessing the removable memory 610 may require removal of aportion of a housing of the accessory 600 or another similar physicalinteraction with the accessory to provide access to the removablememory.

In certain examples, to transfer information contained on the removablememory 610, the removable memory 610 can be removed from the accessory600 and placed into or otherwise operably coupled to another device. Forexample, as shown in FIG. 6B, removable memory 610 can be directlyconnected to a medical device such as defibrillator 620. As describedabove, during treatment of a patient a first medical device can bereplaced or otherwise supplemented with a second medical device. In suchan example, information stored about the patient and any treatmentprovided by the first medical device can be transferred to the secondmedical device using a removable memory as is shown in FIGS. 6A and 6Band described herein.

Referring back to FIG. 6B, the defibrillator 620 can include a processor622 configured to perform one or more instructions during operation ofthe defibrillator as described herein. Additionally, the defibrillator620 can include a data storage 624, a network interface 626, a userinterface 628, a sensing electrode interface 630, a therapy deliverycircuit 632, and a battery 634.

Additionally, as shown in FIG. 6B, the defibrillator 620 can include amemory connector 636 that is configured to operably connect to theremovable memory 610. Upon connection, the processor 622 can access theremovable memory 610 and, if necessary, transfer any informationcontained on the removable memory to, for example, data storage 624 forlocal analysis and processing. For example, if a patient has beenprovided treatment by another medical device, the defibrillator 620 canaccess this information to determine what treatment has already beenprovided to the patient and to continue a similar treatment plan withthe patient, if necessary.

It should be noted that defibrillator 620, and its associated internalcomponents, are provided by way of example only in FIG. 6B. As notedabove, the removable memory 610 can be operably coupled to additionalmedical devices as described herein such as automated ventilators forthe transferring of information as described herein.

In addition to transferring the information contained on removablememory 610 to another accessory or a medical device as shown in FIG. 6B,the information can also be transferred to a computing device or dockingstation that provides a communicative connection to a computing device.As shown in FIG. 6C, information stored on the removable memory 610 canalso be transferred to computing device 650. For example, the computingdevice 650 can be a computer associated with a patient's physician.Following treatment, the physician may want to review the patient'sinformation as stored on the removable memory 610 and as collected bythe accessory 600. The removable memory 610 can be operably coupled to amemory connector 652 that is connected to the computing device 650. Thephysician can then access the information stored on the accessory 600via, for example, a user interface similar to those as described belowin the description of FIGS. 9A and 9B.

It should be noted that the memory connector 652 as shown in FIG. 6C isshown as a separate component by way of example only. Depending upon thetype of memory device used as the removable memory 610, the computingdevice 650 may include a memory connector that provides a directconnection to the removable memory. For example, the removable memory610 may be a USB Type B storage device. In such an example, thecomputing device 650 may include a USB Type B port that can directlyconnect to the removable memory 610.

To fully utilize the patient-coupled resuscitation device or othersimilar accessory-based integrated memory as described herein, one ormore processes can be implemented. For example, FIG. 7A illustrates asample process 700 that provides an overview of using theaccessory-based memory as described herein. As shown in FIG. 7A, one ormore processing devices such as processors 502 and 602 as describedabove and/or processor(s) that are part of the medical device with whichthe accessory is connected can record 702 information collected by oneor more medical device accessories prior to patient treatment. Forexample, the pre-treatment information can include operationalinformation such as battery-specific information as described herein aswell as medical device information (e.g., medical device identification,device type, self-test information, calibration information related to,for example, accelerometers or other similar motion sensors in themedical device, medical device status, etc.). The pre-treatmentinformation can also include patient physiological information andpatient characteristic information such as patient demographic, history,size, gender, weight information and other information that can beaccessed from, for example, the patient's medical record. The processorcan determine 704 whether the patient has been treated. For example,patient treatment information can document a patient receiving one ormore defibrillation or other treatment shocks, receiving chestcompressions, receiving breathing assistance, and other similartreatments as described herein. If the processor does not determine 704that the patient has received treatment, the processor can continue torecord 702 the pre-treatment information.

Though, if the processor does determine 704 that the patient hasreceived treatment, the processor can record 706 treatment informationby, for example, storing the above identified patient treatmentinformation. For example, the treatment information can include whethera defibrillation shock was delivered to the patient and specificinformation about the shock (e.g., what energy level, what the patient'spresenting ECG rhythm was that instigated the particular type oftreatment). The treatment information can also include chest compressioninformation such as compression rate and depth information and/orrelease information, as well as breathing assistance information such asair flow rate information as described herein.

The processor can then determine 708 if the treatment is complete. Ifthe processor determines 708 that the treatment is not complete, theprocessor can continue to record 706 the treatment information. If theprocessor does determine 708 that the treatment is complete, theprocessor can then record 710 any post-treatment information. Forexample, the post-treatment information can include updated operationalinformation such as battery-specific information as described herein aswell as medical device information. The post-treatment information canalso include updated patient physiological information measuredfollowing completion of the patient's treatment.

In certain implementations, the processor can determine 712 whetherthere is a request to transfer the recorded information. For example, ifthe patient-coupled resuscitation device or other similar accessory isoperably coupled to a new medical device, the new medical device canautomatically request a transfer of the recorded information asdescribed herein. If the processor does not determine 712 a request fora transfer of information, the processor can continue to record 710post-treatment information. If the processor does determine 712 arequest for a transfer of data, the processor can transfer 714 at leasta portion of the recorded data to the requesting device.

FIGS. 7B and 7C provide more detailed process flows for various portionsof the process 700. For example, FIG. 7B illustrates process 720 whichincludes a more detailed process flow for monitoring a patient andrecording information prior to, during, and post treatment. FIG. 7Cillustrates process 740 which includes a more detailed process flow fortransferring recorded data to another device.

Referring now to FIG. 7B, the process 720 includes a more detailedprocess flow for monitoring a patient and recording information relatedto the patient prior to, during, and after treatment by a medical devicethat includes a patient-coupled resuscitation device or other similaraccessory having an integrated memory as described herein. For example,as shown in FIG. 7B, a processor such as processors 502 and 602 asdescribed above and/or processor(s) that are part of the medical devicewith which the patient-coupled resuscitation device or other similaraccessory is connected can monitor 722 a patient. For example, theprocessor can access information collected by one or more sensors suchas sensors 504 and 604 as described above to determine currentinformation about the patient such as patient physiological information.The processor can record 724 this pre-treatment patient information, aswell as additional information such as medical device operationalinformation as described herein, to the integrated memory.

While monitoring 722 and recording 724, the processor can furtherdetermine 726 whether the patient is receiving any treatment. If theprocessor determines 726 that the patient is not receiving treatment,the processor can continue to monitor 722 the patient and to record 724pre-treatment information. If the processor does determine 726 that thepatient is receiving treatment, the processor can determine 728additional information about the treatment such as whether the treatmentrequires responder involvement. For example, if the patient is receivingCPR, the processor can determine 728 that the treatment does requireresponder involvement. Conversely, if the patient is receiving adefibrillation shock, the processor may determine 728 that the responderinvolvement is minimal or altogether absent.

If the processor determines 728 that there is no responder involvement,the processor can record 730 information related to the treatment asdescribed herein. However, if the processor does determine 728 thatthere is responder involvement in the treatment, the processor can alsorecord 732 responder performance information as well as record 730 thetreatment information. For example, if the patient is receiving CPR, theresponder performance information can include chest compression rateinformation, average chest compression depth, maximum chest compressiondepth, minimum chest compression depth, release velocity, CPR fraction(e.g., percentage of time that CPR is actually being given to thepatient during periods designated for CPR), percentage of compressiondepth and rate that are within target ranges, and other similarresponder performance metrics.

Upon recording 730 the treatment information, the processor candetermine 734 if the patient is being given additional treatment. If theprocessor determines 734 that the patient is being given additionaltreatment, the processor can again determine 728 whether there isresponder involvement and can record 732 the responder performanceinformation and record 730 the treatment information as noted above. Ifthe processor determines 734 that the patient is not receiving anyadditional treatment, the processor can record 736 any post-treatmentinformation as described herein.

FIG. 7C illustrates process 740 which includes a more detailed processflow for transferring information in response to a request for storedinformation. As shown in FIG. 7C, a processor such as processors 502 and602 as described above and/or processor(s) that are part of the medicaldevice with which the patient-coupled resuscitation device or othersimilar accessory is connected, can establish 742 a connection withanother device such as a medical device or a computing device asdescribed above. The processor can monitor 744 the connection anddetermine 746 whether a request for stored information has been receivedfrom the connected device. If the processor determines 746 that norequest has been received, the processor can continue to monitor 744 theconnection. If the processor does determine 746 that a request forstored information has been received, the processor can determine 748what information has been requested. The processor can then access 750the requested information from the accessory-based memory and transfer752 the requested information to the requesting device.

It should be noted that the processes as shown in FIGS. 7A-7C areprovided by way of example only and can be modified based upon theteachings of the accessory-based memory techniques as described herein.For example, process 720 as shown in FIG. 7B can be altered to removedetermination of the responder involvement if the accessory-based memoryis not configured to store such information or if the accessory isdesigned to operate without responder intervention. Additionally, incertain implementations, process 740 can include encrypting therequested information prior to transferring to the requesting device.

Sample Data Structures

As noted above, a patient-coupled resuscitation device or other similaraccessory such as a set of sensing and therapy electrodes can include anintegrated non-volatile memory that is configured to store informationrelated to the operation or use of the accessory. For example, with aset of sensing and therapy electrodes as described herein, the memorycan be configured to store information measured by and related to theoperation of the set of sensing and therapy electrodes. FIG. 8Aillustrates a sample overview of an electrode information data structure800, which may allow for efficient recording, storage, and retrieval ofinformation. As shown in FIG. 8A, the data structure 800 can includevarious categories of fields such as data identifier fields 805 and datafields 810. Each of the categories of fields can have various fieldsnested therein. For example, data identifier fields 805 can include apatient ID field 805 a, a pre-treatment heartrate field 805 b, apre-treatment blood pressure field 805 c, a treatable arrhythmia field805 d, a treatment shock provided field 805 e, a number of treatmentshocks field 805 f, a first treatment shock information field 805 g, asecond treatment shock information field 805 h, a post-treatmentheartrate field 805 i, and a post-treatment blood pressure field 805 j.While data structures described herein may include static fields thatprovide particular values for certain categories, data structures mayalso include dynamic fields, where larger feeds of data such asphysiological waveforms and other streams of data are recorded overcontinuous period of time. As further shown in FIG. 8A, each individualdata identifier field 805 can have a corresponding data field 810 thatincludes additional information related to the identified piece of data.For example, ID number field 810 a can include a patient identificationnumber such as the patient's social security number, patient recordnumber, insurance information number, and/or other similaridentification that can be used to identify the patient being treated.As shown in FIG. 8A, data field 810 b can include the patient'spre-treatment heart rate information, and data field 810 c can includethe patient's pre-treatment blood pressure information. As further shownin FIG. 8A, data field 810 d can provide an indication of whether thepatient's arrhythmia was treatable, data field 810 e can provide anindication as to whether at least one treatment shock was provided tothe patient, and data field 810 f can provide an indication of how manytreatment shocks were provided to the patient. As further shown in FIG.8A, data field 810 g can provide information related to the firsttreatment shock such as energy delivered and whether the first treatmentshock was successful, data field 810 h can provide information relatedto the second treatment shock such as energy delivered and whether thesecond treatment shock was successful, data field 810 i can provide anindication of the patient's post-treatment heart rate, and data field810 j can provide an indication of the patient's post-treatment bloodpressure.

It should be noted that the information as shown in data structure 800as illustrated in FIG. 8A is provided by way of example only. Inpractice, the data identifier fields 805 as contained within the datastructure 800 can include additional information or remove informationas shown in FIG. 8A. For example, additional data identifier fieldsshowing device identification information such as device serial number,device capability, and device type can be included. In some examples,treatment shock timing information can be provided such as how longafter arrhythmia detection was the first shock delivered, and how longafter the first treatment shock was the second treatment shockdelivered. It should also be noted that two treatment shocks are shownby way of example only. Similarly, the energy delivered values as shownin data fields 810 g and 810 h are provided by way of example only.

Depending upon the type of patient-coupled resuscitation device or othersimilar accessory used, additional data structures can be used to storeinformation related to the operation or use of the accessory. Forexample, FIG. 8B illustrates a sample chest compression information datastructure 820 configured to store information collected from a chestcompression sensor as described herein. As shown in FIG. 8B, the datastructure 820 can include various categories of fields such as dataidentifier fields 825 and data fields 830. Each of the categories offields can have various fields nested therein. For example, dataidentifier fields 825 can include a patient ID field 825 a, a CPRadministered field 825 b, an average compression rate field 825 c, anaverage compression depth field 825 d, a maximum compression depth field825 e, a minimum compression depth field 825 f, a chest compressionfraction field 825 g, a percentage of chest compressions that are withina target depth field 825 h, an average release velocity field 825 i, andan average pre-shock/post-shock pause field 825 j. Or, in someembodiments, the data identifier fields or data structures may store theraw data associated with one or more of the parameters described herein,and the actual calculations for such parameters may be performed by aprocessor external to the accessory, such as a processor on a separatecomputing device, mobile device, and/or server.

As further shown in FIG. 8B, each individual data identifier field 825can have a corresponding data field 830 that includes additionalinformation related to the identified piece of data. For example, IDnumber field 830 a can include a patient identification number such asthe patient's social security number, patient record number, insuranceinformation number, and/or other similar identification that can be usedto identify the patient being treated. As shown in FIG. 8B, data field830 b can include an indication of whether CPR was administered to thepatent, data field 830 c can include a calculated average compressionrate, data field 830 d can include a calculated average compressiondepth, data field 830 e can include a measured maximum compressiondepth, data field 830 f can include a measured minimum compressiondepth, data field 830 g can include a calculated chest compressionfraction, data field 830 h can include a percentage of chestcompressions that were within a target range, data field 830 i caninclude an average release velocity measurement, and data field 830 jcan include average pre-shock and post-shock pause measurements. In someexamples, the data structure 820 can include additional information suchas device identification information including, for example, deviceserial number, device capability, and device type.

In another example, FIG. 8C illustrates a sample airflow sensorinformation data structure 840 configured to store information collectedfrom an airflow sensor as described herein. As shown in FIG. 8C, thedata structure 840 can include various categories of fields such asidentifier fields 845 and data fields 850. Each of the categories offields can have various fields nested herein. For example, dataidentifier fields 845 can include a patient ID field 845 a, a breathingassistance administered field 845 b, a pre-treatment respiration ratefield 845 c, a post-treatment respiration field 845 d, a pre-treatmentend-tidal CO2 field 845 e, a post-treatment end-tidal CO2 field 845 f,average tidal volume 845 g, average minute volume 845 h, percentage ofventilations that are within a target range 845 i, and device ID 845 j.

As further shown in FIG. 8C, each individual data identifier field 845can have a corresponding data field 850 that includes additionalinformation related to the identified piece of data. For example, IDnumber field 850 a can include a patient identification number such asthe patient's social security number, patient record number, insuranceinformation number, and/or other similar identification that can be usedto identify the patient being treated. As shown in FIG. 8C, data field850 b can include an indication of whether breathing assistance wasadministered to the patent, data field 850 c can include a measuredpre-treatment respiration rate, data field 850 d can include a measuredpost-treatment respiration rate, data field 850 e can include a measuredpre-treatment end-tidal CO2 level, and data field 850 f can include ameasured post-treatment end-tidal CO2 level. Data field 850 g caninclude a measured average tidal volume 850 g, data field 850 h caninclude an average minute volume, data field 850 i can include apercentage of ventilations that are within a target range, and datafield 850 j can include device identification information.

It should be noted that the information as shown in data structure 820as illustrated in FIG. 8B and the information as shown in data structure840 as illustrated in FIG. 8C is provided by way of example only. Inpractice, the data identifier fields 825, 845 as contained within thedata structures 820, 840 can include additional information or removeinformation as shown in FIGS. 8B and 8C.

As noted above, a patient-coupled resuscitation device or other similaraccessory can further include a battery having an integratednon-volatile memory. In certain implementations, the integrated memoryof the battery can be configured to store current and historicaloperational information related to the battery. For example, FIG. 8Dillustrates a sample battery information data structure 860 configuredto store information collected from a medical device battery asdescribed herein. As shown in FIG. 8D, the data structure 860 caninclude various categories of fields such as identifier fields 865 anddata fields 870. Each of the categories of fields can have variousfields nested herein. For example, data identifier fields 865 caninclude a battery ID field 865 a, an energy level field 865 b, aself-test information field 865 c, a last alarm information field 865 d,an alarm type field 865 e, a lifetime shocks delivered field 865 f, ashocks delivered since last charge field 865 g, and a device ID field865 h including an indication of what device or devices the battery hasbeen previously used to power.

As further shown in FIG. 8D, each individual data identifier field 865can have a corresponding data field 870 that includes additionalinformation related to the identified piece of data. For example,battery serial number field 870 a can include a manufacturer assignedserial number for the battery. As shown in FIG. 8D, data field 870 b caninclude a current energy level for the battery, data field 870 c caninclude information related to the most recent self-test such as whetherthe test completed and if there were any errors as well as relatedcalibration information such as most recent date of calibration and anyfunctional changes made during the calibration, data field 870 d caninclude information related to the last alarm the battery issued, datafield 870 e can include an indication of what type of alarm was issued,data field 870 f can include a count of how many shocks the battery hasdelivered in its lifetime, data field 870 g can include a count of howmany shocks the battery has delivered since its last charge, and datafield 870 h can include one or more device ID numbers indicating whatdevices the battery has provided power to.

It should be noted that the information as shown in data structure 860as illustrated in FIG. 8D is provided by way of example only. Inpractice, the data identifier fields 865 as contained within the datastructure 860 can include additional information or remove informationas shown in FIG. 8D.

It should also be noted that, in some examples above, the informationcontained in the data fields as shown in FIGS. 8A-8D includes calculateddata. This is provided by way of example only. In some implementations,the patient-coupled resuscitation device or other similar accessorymeasuring the information such as a set of defibrillation electrodes maynot have the processing capabilities to calculate specific informationsuch as that shown in FIGS. 8A-8D and described above. In suchimplementations, the accessory can provide raw recorded data to amedical device or another processing device as described herein forcalculation of the actual values as described herein.

In addition to providing static information such as that shown in FIGS.8A-8D, a patient-coupled resuscitation device or other similar accessorycan also record waveform or other similar time-based information to theaccessory-based memory for, for example, transferring to another devicefor processing and/or analysis. For example, as shown in FIG. 8E, a setof waveforms 880 can be recorded on the memory as raw data fortransferring to another device for processing. Or, such waveform datamay be pre-processed before transferring to another device for furtherprocessing, recording, and/or reporting. As shown in FIG. 8E, thewaveforms can include recorded ECG information, recorded CO2 waveforms,and SpO2 waveforms.

Sample User Interfaces

FIG. 9A illustrates a sample view of a user interface screen 900 thatcan be accessed and utilized by a physician and/or another healthcareprovider to initiate a data transfer of information collected duringtreatment of a patient. For example, the user interface screen 900 canbe used to initiate a transfer of some or all of the data as shown indata structures 800, 820, and 840 and described above in relation toFIGS. 8A-8C. A similar user interface screen can be used, for example,by a medical device manufacturer or a device technician to transfer someor all of the data as shown in data structure 860 in FIG. 8D relating tocurrent and historical operational information for a battery includingan integrated memory as described herein.

As illustrated in FIG. 9A, the user interface screen 900 includes userinterface controls 910, 915, 920, 925, and 930. In some examples, theuser interface control 910 provides access to patient specificinformation such as the cardiac patient's name and an identifierassociated with the cardiac patient. In certain implementations, thepatient identifier can be a medical records number associated with thecardiac patient, an insurance identification number associated with thecardiac patient, a number that directly identifies the cardiac patientsuch as a social security number, or another similar identificationnumber. Based upon the patient specific information, the processor canaccess the patient's medical record. The user interface control 915 caninclude a button or other selectable control. In some examples, theprocessor responds to input selecting the user interface control bytransferring all patient data associated with treatment of the patientand stored on a memory device to the patient's medical record.

Additionally or alternatively, the user interface control 920 canprovide access to a set of available controls 920 a-920 d that can beused to selectively transfer only a portion of the stored information.As shown, the set of available controls can include, for example, a listof available data options as recorded during patient treatment fromwhich the physician can select. For example, as shown in FIG. 9A, theset of controls 920 a-920 d includes a patient physiological datacontrol 920 a, a rescuer performance data control 920 b, a treatmentdata control 920 c, and a device operational data control 920 d. Thephysician can select one or more of controls 920 a-920 d to provide anindication of what data is to be transferred to the patient's record.For example, the physician may determine that the rescuer performancedata should not be transferred to the patient's record. The physiciancan then select controls 920 a, 920 c, and 920 d as described herein.

Additionally or alternatively, the user interface screen 900 can providecontrol 925 that can be used to select an output format for thetransferred information. As shown, a sample set of available outputformats can include a PDF document, a text document, and a spreadsheet.The physician can select one of the options as included in control 925to provide an indication of what format they would like the output ofthe transferred data to be formatted in.

As further shown in FIG. 9A, the user interface control 930 includes aset of selectable buttons. In response to receiving a selection of the“submit” button, the processor can transfer data to the patient's recordas indicated or selected in controls 920 a-920 d. In response toreceiving a selection of the “clear” button, the processor can deleteexisting selections and/or entered information from the user interfacescreen 900. In response to receiving a section of the “cancel” button,the processor can abort the data transfer process.

FIG. 9B illustrates a sample view of a user interface screen 940 thatcan be accessed and utilized by a physician and/or another healthcareprovider to immediately access and view some or all of the informationcollected during treatment of a patient. For example, the user interfacescreen 940 can be used to view some or all of the data as shown in datastructures 800, 820, and 840 and described above in relation to FIGS.8A-8C. A similar user interface screen can be used, for example, by amedical device manufacturer or a device technician to view some or allof the data as shown in data structure 860 in FIG. 8D relating tocurrent and historical operational information for a battery includingan integrated memory as described herein.

As illustrated in FIG. 9B, the user interface screen 940 includes userinterface controls 945, 950, 955, and 960. In some examples, the userinterface control 945 provides access to patient specific informationsuch as the cardiac patient's name and an identifier associated with thecardiac patient. In certain implementations, the patient identifier canbe a medical records number associated with the cardiac patient, aninsurance identification number associated with the cardiac patient, anumber that directly identifies the cardiac patient such as a socialsecurity number, or another similar identification number. Based uponthe patient specific information, the processor can access the portionof stored information that is related to the identified patient. Theuser interface control 950 can include a button or other selectablecontrol. In some examples, the processor responds to input selecting theuser interface control by providing all patient data associated withtreatment of the patient and stored on a memory device for immediateviewing.

Additionally or alternatively, the user interface control 955 canprovide access to a set of available controls 955 a-955 d that can beused to selectively view only a portion of the stored information. Asshown, the set of available controls 955 a-955 d can include, forexample, a list of available data options as recorded during patienttreatment from which the physician can select. For example, as shown inFIG. 9B, the set of controls 955 a-955 d includes a patientphysiological data control 955 a, a rescuer performance data control 955b, a treatment data control 955 c, and a device operational data control955 d. The physician can select one or more of controls 955 a-955 d toprovide an indication of what data the physician would like to view. Forexample, the physician may determine they are not interested in therescuer performance data. The physician can then select controls 955 a,955 c, and 955 d as described herein for immediate viewing.

As further shown in FIG. 9B, the user interface control 960 includes aset of selectable buttons. In response to receiving a selection of the“submit” button, the processor can access and display the information asindicated or selected in controls 955 a-955 d. In response to receivinga selection of the “clear” button, the processor can delete existingselections and/or entered information from the user interface screen940. In response to receiving a section of the “cancel” button, theprocessor can abort the data viewing process.

It should be noted that the user interface screens 900 and 940 as shownin FIGS. 9A and 9B are provided by way of example only and can bemodified based upon the design and intended functionality of theinformation accessing system. For example, user interface screen 900 canfurther include a control that provides the physician with an option toselect a download location for a file transfer. Similarly, userinterface screen 940 can include a control that provides the physicianwith an option to select how to view the information.

Chest Compression Sensor Embodiments

A variety of chest compression sensors can be used in conjunction withthe examples described herein. For instance, in some examples, chestcompression sensors that are distinct from other medical equipment areprovided. In these examples, to decrease the amount of time required toutilize the chest compression sensor in the administration oflife-saving CPR, some of the chest compression sensors are configured toautomatically initiate operation as needed.

FIG. 10A illustrates one example of such a chest compression sensor, thecompression sensor 1000. As shown in FIG. 10A, the compression sensor1000 includes a housing 1002, a connector 1004, and a photoelectricsensor 1006. The connector 1004 can include a pigtail style connectorand can transport power and data for use by the other components of thecompression sensor 1000. In some examples, the photoelectric sensor 1006can detect ambient light and can transmit a detection signal where theambient light transgresses a threshold value (e.g., 1000 lux). In someexamples, the compression sensor 1000 includes additional circuitry(e.g., a microcontroller or other processor) that is coupled to thephotoelectric sensor 1006. The additional circuitry can be configured tomonitor an output of the photoelectric sensor 1006 for the detectionsignal. In these examples, the additional circuitry is furtherconfigured to initiate powered operation of the compression sensor 1000in response to receiving the detection signal.

FIG. 10B illustrates another example chest compression sensor 1010 inaccordance with some examples. As shown in FIG. 10B, like thecompression sensor 1000, the compression sensor 1010 includes a housing1002 and a connector 1004. The compression sensor 1010 further includesa low-power or self-powered accelerometer 1012. In some examples, theaccelerometer 1012 can detect movement and can transmit a detectionsignal where the movement transgresses a threshold value (e.g., movementsufficient to administer a CPR compression). In certain implementations,the accelerometer 1012 can be calibrated to configure the outputresolution of the accelerometer to accurately translate an outputvoltage of the detection signal of the accelerometer to motioninformation. The calibration can include applying a known force to theaccelerometer 1012 and adjusting the output voltage of the detectionsignal to an expected result. Calibration information such as the dateof the calibration and changes applied to the output voltage of thedetection signal can be recorded as medical device information asdescribed herein.

In some examples, the compression sensor 1010 includes additionalcircuitry (e.g., a microcontroller or other processor) that is coupledto the accelerometer 1012. This additional circuitry is configured tomonitor an output of the accelerometer 1012 for the detection signal. Inthese examples, the additional circuitry is further configured toinitiate powered operation of the compression sensor 1000 in response toreceiving the detection signal. Other examples are provided herein of achest compression sensor that initiates compression sensing uponactuation of a switch or when a sufficient amount of force is detected.In some embodiments, the chest compression sensor may include acapacitive force sensor that initiates operation of the compressionsensing functionality upon reaching a threshold force (e.g., between 440and 560 Newtons) such as when the sensor is first subject tocompressions. Or, the sensor may include a plastic tab over a batterysuch that when the tab is pulled, the sensor becomes ready foroperation. In other embodiments, the chest compression sensor mayinclude a hall sensor and nearby magnet located within the casing thattriggers compression sensing once the hall sensor detects disconnectionfrom the magnet. Another embodiment may employ a plastic tab designed tobreak upon first compression or a membrane switch triggers compressionsensing in the device when pushed.

To be effective, CPR should begin within a very short period of time(e.g., 1-5 minutes) after the onset of cardiac arrest. This requirementcan make it difficult to identify and use a defibrillator/monitor insufficient time so as to provide CPR feedback for the caregiver. Inaddition, such cardiac arrests are oftentimes respiratory in nature, notrequiring defibrillation electrodes. Due at least in part to thesefactors, devices described herein that provide monitoring of CPRmetrics, including a standalone chest compression sensor, may be able torecord immediately upon start of CPR without requiting a device to be inthe vicinity. Hence, in accordance with embodiments provided herein, thechest compression sensor may itself have measurement, processing, andstorage capabilities. Also described herein, the standalone sensor mayinclude a basic level of output feedback, such that a nearby screen isnot required. This could be an LCD/E-Ink screen, a set of LED lights, avibration actuator, and/or a speaker integrated with the chestcompression sensor device. Although it can be appreciated that thestandalone chest compression sensor may be able to connect to acompanion screen in the form of a tablet, display, medical deviceinterface and/or other mode of feedback.

Neo-natal CPR possess special challenges to caregivers due to thediminutive anatomy of the patients. Further, these patients have fragileand sensitive skin, which often makes it undesirable to attach adhesiveor abrasive materials typically found in traditional monitoringequipment that could bring harm to their skin. Accordingly, traditionalchest compression sensors which come with a defibrillator/monitor thatare intended for use with adults present difficulties in providingeffective chest compressions to the patient. As such, some examplesdescribed herein provide for chest compression sensors designed toovercome these challenges.

FIG. 11A illustrates one example of a chest compression sensor 1100 thatincludes features configured to provide better CPR treatment toneo-natal patients. As shown in FIG. 11A, the compression sensor 1100,like the compression sensor 1000, includes a housing 1002 and aconnector 1004. The compression sensor 1100 further includes an elasticband 1102 that is configured to expand while being fitted to a patientand then contract to provide a snug fit with minimal lateral movement.For instance, in some examples, the elastic band 1102 is sized to have aresting diameter of approximately 2-5 inches. In this way, thecompression sensor 1100 more easily and reliably remains in its fittedlocation, thereby providing for more accurate CPR readings. Accuracy ofCPR performance, such as proper compression depth, is particularlyimportant when dealing with neo-natal patients.

FIG. 11B illustrates one example of a chest compression sensor 1110 thatincludes additional features configured to provide better CPR treatmentto neo-natal patients. As shown in FIG. 11B, the compression sensor1110, like the compression sensor 1100, includes a housing 1002 and anelastic band 1102. The compression sensor 1110 further includes opposingaccelerometers 1112 and 1114 that are configured to detect movementtoward and away from one another. In some examples, the compressionsensor 1110 includes additional circuitry (e.g., a microcontroller orother processor) that is coupled to the opposing accelerometers 1112 and1114. This additional circuitry is configured to monitor outputs of theopposing accelerometer 1112 and 1114 for the motion signals. Byprocessing motion signals sourced from anterior and posterior locationson the patient, the additional circuitry can generate more precise andaccurate CPR readings, which are of particular importance to neo-natalpatients. For example, when performing neo-natal CPR, it is often thecase that the thumbs of the caregiver are positioned on the anteriorchest of the patient and the fingers of the caregiver are positioned onthe posterior of the patient. By having motion sensors at both theanterior and posterior regions of the patient, a more accuratedetermination of chest compression depth can be made.

FIG. 12A illustrates one example of a chest compression sensor 1200 thatincludes additional features configured to provide better CPR treatmentto neo-natal patients. As shown in FIG. 12A, the compression sensor1200, like the compression sensor 1000, includes a housing 1002 and aconnector 1004. The compression sensor 1200 further includes a strap1202 and a strain gauge 1204. The strap 1202 forms a series of aperturesthat are sized and shaped to receive a post on a distal portion of thestrap 1202. In this way, the strap 1202 provides for the compressionsensor 1200 to be snugly fitted to the thorax of variously sizedpatients, including neo-natal patients. The strain gauge 1204 can detectdeformation of the strap 1202 and can transmit a signal indicative ofthe deformation. In some examples, the compression sensor 1200 includesadditional circuitry (e.g., a microcontroller or other processor) thatis coupled to the strain gauge 1204. This additional circuitry isconfigured to monitor outputs of the strain gauge for the deformationsignals. By processing deformation signals, the additional circuitry cangenerate more precise and accurate CPR readings, which are of particularimportance to neo-natal patients. In certain implementations, acalibration curve may be used to correlate the diameter of the strapwith the amount of strain on the strap, making it possible to monitorpatient circumference and estimate absolute chest depth of compressionand chest deformation that may occur from chest remodeling/deformationthat occurs during compressions. FIGS. 12B and 12C illustrate twoexamples of chest compression sensors 1210 and 1220 that includesadditional features configured to provide better CPR treatment toneo-natal patients. As shown in FIG. 12B, the compression sensor 1210,like the compression sensor 1000, includes a housing 1002 and aconnector 1004. The compression sensor 1210 includes a strap 1212 thatincludes a buckle closure. The buckle closure can include a receptacle1213 and an insert 1214. As shown in FIG. 12B, the insert 1214 ispositioned adjacent to the compression sensor housing 1002. Such anarrangement allows for a CPR administrator to position the compressionsensor 1210 properly on the patient's sternum while buckling the strap1212. Thus, a need to adjust the position of the compression sensor 1210once affixed to the patient's thorax is reduced, thereby reducing theoverall time required before CPR can be administered to the patient.

As shown in FIG. 12C, the compression sensor 1220, like the compressionsensor 1000, includes a housing 1002 and a connector 1004. Thecompression sensor 1220 further includes a strap 1222. The strap 1222includes a ratchet closure for affixing the compression sensor 1220 to aneo-natal patient. In some examples, the rachet closure can includemeasurement indicators that enable a CPR administrator to easily measurethe circumference of the neo-natal patient's thorax, which can behelpful in diagnosing certain conditions.

It should be noted that the adjustable closures as shown in FIGS.12A-12C are provided by way of example only, and additional adjustableclosures can be used. For example, a slidable connector, a hook-and-loopconnector, and other similar adjustable connectors can be included onthe straps as described above to provide for an adjustable fit for acompression sensor.

Use-Case Examples

In an example, a cardiac patient may experience an arrhythmia whilewalking through a public space such as a shopping mall. Upon noticingthe patient experiencing the arrhythmia, a bystander can step in as afirst responder. The first responder can access an AED that is mountedon the wall nearby and open the therapy pad attached to the AED Thefirst responder can remove the patient's shirt and position the therapypad on the patient's chest, following the instructions as printed on thepad. The first responder can then activate the AED. The AED may issue analert including a verbal warning that the AED is monitoring the patientand may provide treatment. The AED may also provide an indication thatthe patient is not experiencing an arrhythmia that is treatable with atherapy shock and that the patient should be administered CPR. The firstresponder, or another bystander that is trained in CPR, may begin toadminister CPR to the patient. After some time, the patient may improveor continue to deteriorate. If the patient continues to deteriorate, theAED may determine that the patient can now be treated with adefibrillation shock and issue warning as such. The AED may then deliverthe shock to the patient via the therapy pad. During monitoring andtreatment of the patient, an integrated memory in the therapy pad isrecording pre-treatment information, treatment information, andpost-treatment information as described herein.

At some point in the above example, trained medical responders arrive onthe scene and take over treatment of the patient. The trained medicalresponders can disconnect the therapy pad from the AED and connect to adefibrillation device they brought. The information stored in the memoryof the therapy pad can be automatically loaded onto the newdefibrillation device which can continue treatment in line with theprior treatment delivered by the AED.

To continue the above example, the trained emergency responders cantransfer the patient to the hospital, continuing to provide treatment tothe patient on the way to the hospital. Upon arrival at the hospital,the patient may be disconnected from any portable equipment brought bythe emergency medical responders and connected to hospital equipment. Insuch an example, a removable memory such as a battery having anintegrated memory or a removable memory device as described herein canbe removed from the trained emergency responder's equipment andtransferred to the hospital equipment. Similar to above, the hospitalequipment can access patient and treatment information for the patientand continue an appropriate course of treatment for the patient.

In another example, a removable memory associated with a medical devicecarried by a trained emergency responder can be accessed to evaluate theperformance of the responder. For example, data collected by a chestcompression sensor can be accessed and evaluated to determine howefficiently and effectively the responder is performing CPR on patients.

In another example, a physician may wish to analyze patient data fromimmediately before the patient was treated for an arrhythmia. Thephysician can access a removable memory from, for example, a therapy padthat includes physiological information for the patient as collectedimmediately prior to treatment of the patient. As described herein, thephysician can access the information and review information such as ECGmetrics for the patient immediately before the patient was treated.

Example Medical System Overviews

FIG. 13A is a schematic illustration of an example of a patientmanagement and treatment system 1300, including a medical device 1402(e.g., patient monitoring device such as an automated externaldefibrillator or professional style monitor/defibrillator as describedherein), electrode assembly 1310, and rescuers 1304, 1306 providingmedical treatment to a patient 1302. While several embodiments presentedherein describe the medical device 1402 as implementing the processor(s)for analyzing data from the sensor(s), determining next steps in thetreatment procedure, and providing output via a user interface, it canbe appreciated that other portable computing devices such as a tablet orother computing device can perform steps in accordance with the presentdisclosure. Additionally, the portable computing devices can be used inconjunction with medical device 1402.

In this example, rescuers 1304, 1306 are in position and providing careto the patient 1302, with rescuer 1304 providing chest compressions tothe torso of the patient 1302, and rescuer 1306 providing ventilationusing ventilation bag 1312, which is connected to a ventilation valve1313 and a mask 1315. As noted above, these components (1312, 1313,1315) are often collectively referred to as a bag-valve-mask (BVM).While not illustrated, the BVM is often connected to a source of“medical oxygen,” which is used as an oxygen supply to the bag 1312, sothat oxygen can be delivered during ventilation.

Generally, the rescuers 1304, 1306 can be lay-rescuers who were near thepatient 1302 when the patient required care, or may be trained medicalpersonnel such as doctors, firefighters, paramedics, combat medics, oremergency medical technicians, for example. Although two rescuers 1304,1306 are illustrated, in alternative embodiments additional rescuers(not shown) may also be involved in treating the patient or only onerescuer may provide treatment. As used hereinafter, the term rescuer maygenerally be understood to include a person that is aiding in acute caretreatment of the patient 1302 during an emergency medical situation andmay be actively engaged in resuscitation activity of the patient, suchas in providing cardiopulmonary resuscitation. Additionally, similarterms such as clinician, user, or caregiver are generally understood tobe interchangeable when used herein to describe a person giving acutemedical and/or resuscitative aid to the patient.

Additionally, while the present system is described with respect to aBVM and manual ventilations, a portable automatic ventilator could beused to provide oxygen and ventilate the patient. The EMV+® or Z Vent™,both manufactured by ZOLL Medical Corporation of Chelmsford, Mass. areexamples of portable ventilators. Likewise, the rescue scenario mayoccur in a hospital or ambulance where an automatic ventilator may alsobe available (e.g., ZOLL 731 Ventilators provided by ZOLL MedicalCorporation).

Control and coordination for the medical event is typically controlledby the medical device 1402. In a typical implementation, the medicaldevice 1402 is a defibrillator, automated external defibrillator (AED),ventilator system, or medical patient monitor, to list a few examples.Alternatively, the medical device 1402 could even be mobile computingdevice such as a tablet-based computer, smartphone, or wearablecomputing and interface device (e.g., smart watch or head mountedoptical display) that is controlled by the rescuers 1304, 1306, forexample, in coordinating resuscitation activities, evaluating orotherwise communicating with on-site and/or remote medical personnel, orotherwise providing information useful for the rescuer(s) in treatingthe patient.

The medical device 1402 is connected to an electrode assembly 1310 via awired connection 1319 from the medical device to the electrode assembly1310. In this implementation, the medical device (e.g., defibrillator,or patient monitor) can take a generally common form, and may be aprofessional style defibrillator which can also function as a medicalmonitor, such as the R-SERIES®, X-SERIES®, M-SERIES®, or E-SERIES®provided by ZOLL Medical Corporation of Chelmsford, Mass., a ventilator(e.g., portable ventilator), such as the 731 Ventilator provided by ZOLLMedical Corporation, or an automated external defibrillator (AED), suchas the AED PLUS®, or AED PRO® provided by ZOLL Medical Corporation.

In addition, the medical device 1402 could take the form of anintegrated system of devices (defibrillator, vital signs monitor,ventilator, or mechanical CPR chest compression device, for example)with either a composite, single-system embodiment or one that uses aseries of discrete devices that are dynamically integrated through wiredand/or wireless communication to function as a single integrated system.

This optionally wired connection 1319 enables data from sensors in theelectrode assembly to transmit information to the medical device 1402,and the wired connection 1319 also allows energy to be sent from themedical device 1402 to the electrode assembly 1310, in scenarios inwhich the medical device is a defibrillator or automated externaldefibrillator. In alternative embodiments, for example, in scenarios inwhich the medical device is a tablet or monitor, the wired connectionmay be replaced with a wireless connection. While not expressly shown inthe figures, the BVM component(s) as well as other treatment and/orsensing devices (e.g., oxygen saturation sensors, accelerometers, airflow sensors) can also be communicatively coupled with the medicaldevice 1402. For example, in embodiments where the BVM incorporatessensors (e.g., oxygen sensor, capnography, flow sensor, air flowmodule), such sensors can be in communication with the more centralmedical device 1402. As noted herein, sensors for obtaining datarelevant to gas parameters characteristic of the patient airway can beprovided as separate components or can be integrated together into asingle component.

The electrode assembly 1310 is shown on the patient 1302 in a typicalposition. The electrode assembly 1310, in this example, is an assemblythat combines an electrode positioned high on the right side of thepatient's torso, a separate electrode positioned low on the left side ofthe patient's torso, and a sensor package located over the patient'ssternum. The electrode assembly 1310 can further include a sensorpackage, which, in this example, is obscured in the figure by the handsof rescuer 1304. This sensor package can include a motion sensor (e.g.,accelerometer(s), velocity sensor, distance sensor) or similar sensorpackage that can be used in cooperation with a computer in the medicaldevice 1402 to monitor performance (e.g., compression depth, compressionrate, and release) of the chest compressions, patient movement orpositioning. Additionally, a microphone can also be included with, orseparately from, the electrode assembly 1310 to obtain auscultation data(e.g., acoustic signals) of internal sounds of the patient 1302. Themicrophone can be used to obtain signals related to heart sounds,breathing sounds or gastric sounds, for example.

In the illustrated example, the medical device 1402 communicateswirelessly with the wrist-worn devices 1320, 1322 to present informationand/or guidance to the rescuers 1304, 1306. For example, informationrelated to chest compressions, heart rate, or other relevant information(e.g., SpO2, ETCO2) related to the intubation process can be visuallypresented on the displays 1321, 1323. Additionally, vibration componentsand/or audible sound generators on the wrist-worn devices 1320, 1322 canprovide feedback. Such feedback can include information about physicalstatus of the patient 1302, guidance and feedback related to ventilationor cardio pulmonary resuscitations of the patient 1302, and/or specificcontext-sensitive or prioritized instructions to perform criticalinterventions/tasks to ensure patient safety or optimal therapeuticmanagement. Haptic and audible feedback can have the added benefit ofproviding a notification to the rescuer while not requiring the rescuerto divert his/her attention from the task at hand. This is as opposed toa visual display, which would typically require the rescuer to turnhis/her head to view whatever is presented on the visual display.

In still yet another embodiment, the rescuers may use head-mountedheads-up display systems (not shown). The benefit of wearable heads-updevices is that they allow focus to remain on the patient 1302 while atthe same time providing a continuous interface to relevant data.

FIG. 13B is a schematic illustration of an example of the airwaymanagement system 1300, including the medical device 1402, electrodes,and endotracheal tube 1329 post intubation. That is, duringpost-intubation, the ET tube has been placed in the trachea of thepatient and the patient is being physiologically monitored whileventilations are administered (e.g., by a BVM or ventilator).

In general, a tracheal tube is a catheter that is inserted into thetrachea of patient 1302 to establish and maintain an open airway and toensure adequate exchange of oxygen and carbon dioxide. An endotrachealtube, such as the endotracheal tube 1329, is a specific type of trachealtube that is usually inserted through the patient's mouth or nose. Manyairway tubes such as an endotracheal tube 1329 can be used withembodiments of the present device to provide a patent airway forventilation and monitoring.

The ventilation bag 1312 is coupled to the ventilation valve 1313. Asshown in this example, the mask is no longer required once theendotracheal tube is inserted into the patient. In accordance withembodiments of the present disclosure, one or more airway sensors 1327(e.g., can include one or more of oxygen sensor, capnography sensor,flow sensor, etc.) can be situated between the ventilation bag 1312 andthe endotracheal tube 1329 to allow monitoring of the inspiratory andexpiratory gas, for example, as a result of manual ventilation performedusing the ventilation bag 1312, and/or monitoring of patient breathing.As is typical, the ventilation bag 1312 and valve 1313 allow the rescuerto actively ventilate the patient 1302 by squeezing the bag or for thepatient to spontaneously breathe, while in both instances the patient'sexhaled gas exits back through the valve allowing for bidirectionalmonitoring. Alternatively, the ventilation bag 1312, can be augmented toprovide supplemental O2 from a separate O2 source (e.g., oxygen tank).

In the illustrated embodiment, the airway sensor(s) 1327 includes one ormore sensors to measure various physiologic and/or airway gasmeasurement signals during both inspiration and expiration thatincludes: oxygen (O2), carbon dioxide (CO2), gas flow rate and volume,airway pressure, gas temperature, and gas humidity, to list a fewexamples. Additionally, processing resources in either the airwaysensor(s) 1327 or medical device 1402 are able to calculate additionalphysiologic and/or airway gas measurement parameters such as breathvolume, breathing rate, O2 consumption, CO2 elimination rate,respiratory quotient, airway leak and other calculated values, forinstance.

Communication cable 1317 can be any type of communication cable or setof wires, which allows data exchange between the medical device 1402 andthe airway sensor(s) 1327 such as but not limited to an RS-232 cable,Universal Serial Bus (USB) cable or Ethernet cable. Communicationbetween the medical device 1402 and the airway sensor(s) 1327 could alsobe wireless communication such as IEEE 802.11 wireless local areanetwork (WLAN) or low-power radio frequency (RF) communication such asBluetooth, to list a few examples.

Electrodes 1325 a and 1325 b are electrically coupled to the medicaldevice 1402 using cables 1319 a and 1319 b. Electrodes 1325 a and 1325 bare positioned across the subject's thoracic cavity and attached to thesubject, one electrode anterior and the other electrode posterior to thepatient, for example. In the embodiment, electrodes 1325 a and 1325 bare capable of measuring an electrocardiogram (ECG) signal from thepatient. The electrodes 1325 a and 1325 b can also be suitableelectrodes for measuring a transthoracic impedance of a subject. In someembodiments, the electrodes 1325 a, 1325 b can be high-voltageelectrodes capable of transmitting electrotherapy to the patient, suchas for electrical defibrillation and/or cardiac pacing treatment.

The medical device 1402 is configured with electrodes 1325 a and 1325 bthat are capable of providing therapeutic shocks, if needed, as well asto monitor changes in the transthoracic impedance of the patient 1302.If the endotracheal tube 1329 is properly placed in the subject'strachea and the subject's lungs are ventilated using a ventilation bag1312 and valve 1313 (or via a mechanical ventilator), then the medicaldevice 1402 detects a change in impedance across the subject's thoraxbetween electrodes 1325 a and 1325 b. If the endotracheal tube 1329 isnot properly placed; for example, it was placed in the subject'sesophagus, or has become dislodged, the medical device 1402 will detectthat the impedance change across the subject's thorax does not indicatethat effective ventilation is being administered and can alert the userwith a context-sensitive alarm message using audible and/or visual alarmindicators on the medical device 1402. Alternatively, or in addition, acapnography sensor is provided in the patient airway (e.g., mainstreamor sidestream). In this embodiment, if the endotracheal tube 1329 isproperly placed in the subject's trachea, then the medical device 1402detects CO2 (e.g., end tidal CO2 or ETCO2) indicative of proper tubeplacement; and if the endotracheal tube 1329 is not properly placed orhas become dislodged, the medical device 1402 will fail to detect CO2waveform indicative of proper intubation, and can alert the user with acontext-sensitive alarm message using audible and/or visual alarmindicators on the medical device 1402. The medical device 1402 can be incommunication with other devices, such as wrist-worn devices 1320, 1322,heads up display devices, for example, for alerting the necessarycaregiver(s).

FIG. 14 is a block diagram of a patient treatment system 1400, includingthe medical device 1402, airway sensor(s) 1327, device sensors1410-1422, which measure intubation parameters, peripherals (e.g.,ventilator 1423 and portable computing device 1425), and a centralfacility 1424. The medical device 1402 typically includes a processor1404 for executing instructions of software running on the medicaldevice 1402, memory 1409 to store the software and sensor informationreceived from the sensors, a signal acquisition unit 1408 to receivesensor information from the sensors 1410-1422, and an output device 1406to provide feedback to the rescuers, which is typically a display. Theoutput device 1406 can further include one or more speakers forproviding audible feedback, or other components for providing othertypes of feedback, such as haptic/tactile. Generally, a suitable displaycan be made from a wide variety of materials as described above.Additionally, the screen can be touchscreen display, which is a combinedinput/output device, which enables user interaction of the medicaldevice 1402 by touching the output device 1406.

Additionally or alternatively, the patient treatment system 1400 canfurther include a portable computing device 1425 (e.g., tablet,smartphone, laptop computer) in communication with the medical device1402. In one example, the portable computing device 1425 can mirror thedisplay of the medical device 1402 or can provide a secondary display ofinformation relevant to the user of the portable computing device 1425.For instance, in certain situations, the activities of different usersat the emergency scene can differ, hence, it can be preferable for eachof the displays (e.g., on the medical device, on the portable computingdevice, on another device, etc.) to differ according to the jobperformed by the associated user. Additionally, the portable computingdevice 1425 can include general information (e.g., dosage charts),medical procedure checklists, and/or other protocols that are typicallyused during an intubation procedure. Additionally, it can includeadditional checklists and/or protocols for other medical situations(e.g., instructions on the performance of CPR, or instructions on how toassemble the BVM, how to hook the patient up the ventilator, and othersimilar instructions). Additionally, the portable computing device wouldprovide a quality assurance report that includes: a list of completedand uncompleted tasks, the time tasks were completed, the required timefor each of the tasks, event markers, alarms that occurred, relevantphysiologic data as well as other data that demonstrates the performanceof the procedure.

Additionally, the portable computing device 1425 can include the abilityto allow the user to enter patient information (e.g., height, weight,and gender) via a touchscreen display. The portable computing device canalso include internet connectivity (e.g., via Wi-Fi or 3G/4G wirelessmobile telecommunication networks) to enable the rescuer to accessadditional patient information from the central facility, for example.

Respiratory gas monitoring provides a noninvasive method to monitor arange of physiologic or airway gas measurement data that indicates thepattern of ventilation, its effectiveness, the patient's metabolicstate, endotracheal tube placement and cardiopulmonary functioning. Thepresent system embodies a multifunction sensor module; however, themedical device 1402 is also capable of providing the performance using aseries of individual sensor modules to measure O2 and CO2 gasconcentrations, gas flow and airway pressure.

An oxygen sensor 1410 typically measures the amount of oxygen present inthe flow of gas through the patient's airway, and can be used to measuregas parameters in accordance with the present disclosure. The oxygensensor can be equipped to measure the proportion of oxygen in the gasbeing analyzed. An example of an oxygen sensor that can be incorporatedas an airway sensor is the Fibox 4 trace provided by PreSens PrecisionSensing from Regensburg, Germany. Accordingly, when the oxygen sensor isplaced in the patient airway, a percentage or amount readout of oxygenthat is present within the airway can be recorded. In one embodiment,the oxygen sensor is attached to an inner surface of another airwaysensor, such as a flow sensor or capnography sensor, or can be locatedelsewhere along the patient airway. Oxygen is measured contactlessthrough a transparent vessel wall. Preferably, the sensor has ameasurement range of oxygen. In an embodiment, an oxygen sensitivecoating can be immobilized on a 125 μm flexible transparent polyesterfoil. In addition, the sensor could also use other oxygen measurementmethods such as a galvanic cell or paramagnetic techniques for example.

A pulse oximeter 1412 that provides a measurement of the oxyhemoglobinsaturation of the patient can be used to measure physiologicalparameters in accordance with embodiments described herein. Typically,the pulse oximeter is attached to the patient's finger, but could alsobe attached to other locations (e.g., finger, palm, toe, sole or ear,for example). In such cases, the sensor is typically placed at a thinpart of the patient's body, such as the fingertip or earlobe, and thedevice passes multiple wavelengths of light through the body to aphotodetector on the other side. The changing absorbance at each of thewavelengths can allow for the medical device/sensor to determine therespective absorbance due to pulsing arterial blood. Alternatively, orin addition, a near infrared sensor for measuring muscle oxygenationcontent and tissue pH could also be implemented to monitor the effectiveblood flow and tissue oxygenation. Rather than detection throughtransmission, the reflectance of the multiple wavelengths of light bythicker tissues allow for levels of oxygen at that location to bemeasured. In the illustrated example, the electrocardiogram sensors 1414are part of the defibrillator electrodes and measure electrical activityof the patient's heart, although it can be appreciated that ECG leadsseparate from the defibrillation electrodes can be employed. Anaccelerometer 1416 or other motion sensor can be employed to measuremovements of the patient and/or rescuer, for example, in moving thepatient or applying chest compressions to the patient. In alternativeembodiments, the motion of the patient could be sensed by a sternalcompression sensor, which is part of the electrode assembly 1310 or aseparate component entirely. Additionally, the accelerometer could belocated on the tube 1329 (e.g., at a proximal location) or the rescuers1304, 1306.

A flow sensor 1421 for measuring the flow rate and volume of air flowingthrough the patient's airway can be used to measure gas parameters inaccordance with various embodiments. The flow sensor 1421 is typicallylocated within the airway of the patient, in fluid communication withthe portable ventilator or BVM 1423. The flow sensor can be incommunication with the medical device and, hence, can provideinformation concerning the flow rate and volume in the patient's airway.Any suitable flow sensor can be employed, such as for example, adifferential pressure sensor. The flow sensor can be similar to thatdescribed in U.S. Patent Publication 2017/0266399, entitled “Flow Sensorfor Ventilation,” which is hereby incorporated by reference in itsentirety. Accordingly, the flow sensor can provide measurements ofinspiratory flow to the patient (e.g., provided by positive pressurebreath ventilations) and expiratory flow from the patient (e.g., airbreathed out from the patient).

One or more airway sensors 1327 can be employed, for monitoring variouscharacteristics of the air flow within the patient's airway. The airwaysensor(s) can include a capnography sensor 1418. For example, thecapnography sensor 1418 can be equipped to measure gas parameters, suchas the concentration and partial pressure of carbon dioxide (CO2) in therespiratory gases of the subject. Signals/data from the capnographysensor 1418 can be further processed to determine physiologicalparameters, such as end-tidal CO2 of the patient. In addition, theairway sensor(s) can include a flow sensor that communicates informationrelated to the subject's inspiratory and expiratory gas flow. The airwaysensor(s) can further communicate information related to theconcentration and partial pressure of respiratory gases, oxygen andwater vapor for example. As discussed herein, the airway sensor(s) caninclude, for example, capnography for measuring CO2, an oxygen sensorfor measuring the amount of oxygen, and/or a flow sensor for measuringthe rate and volume of flow within the patient's airway, separate orintegrated together.

While the illustrated embodiment identifies certain types of sensors,those skilled in the art will recognize that additional sensors could beimplemented as well. Likewise, while the specification identifiesspecific intubation parameters in describing various examples of presentsystem, alternative sensors which perform identical or similar functionscan be implemented for enabling the medical device to determine whethersteps in an airway management procedure have or have not been completed,for effectively assisting the rescuer in properly carrying out theprocedure.

The medical device 1402 can include additional components such as amicrophone 1420 to capture acoustic information of the patient 1302 suchas the sounds of the patient breathing or sounds of their heart beating.Additionally, or alternatively, the medical device can further includeone or more microphones to capture voice commands from the rescuers1304, 1306.

Furthermore, a video laryngoscope 1422 is also connected to the medicaldevice 1402, which can provide information used as a positioningparameter for the airway management system to determine the current stepin the RSI procedure. Laryngoscopes enable rescuers to look at the backof the throat (oropharynx), voice box (larynx) and identify the vocalcords, which provide the critical landmark for insertion of anendotracheal tube into the trachea. Use of a video laryngoscope aids theuser in visualizing critical anatomy while also allowing a range ofpatient-rescuer positions from which to view the airway and insert theendotracheal tube. Additionally, the video laryngoscope provides for adigital recording of the procedure that allows for secondaryconfirmation of tube placement and post-case review. In an alternativeembodiment, the digital recording from the laryngoscope would allow foruse of image analysis that could provide additional confirmation thatthe endotracheal tube was properly placed.

In one embodiment, the medical device 1402 communicates with a centralfacility 1424. The communication between the central facility 1424 andmedical device can be via wireless technologies, like Bluetooth, orwireless telephone networks (e.g., 3G/4G wireless mobiletelecommunication networks), or possibly even the Enhanced 911 (or E911)network. The wireless networks are typically secured that requirepassword authentication to access the wireless network. The centralfacility 1424 can be third-party location that stores and/or analyzesinformation received from the medical device 1402. The central facilityis generally an emergency response center (e.g., 9-1-1 dispatch),back-end component such as a server, hospital, or ambulance, to list afew examples.

Referring to FIG. 15 , examples of components of a medical device 1510and are shown schematically. The medical device 1510 can include aprocessor 1520, a memory 1521, one or more output devices 1530, one ormore user input devices 1544, and a communications interface 1545. Thecommunications interface 1545 can include any of a variety oftransmitters and/or receivers. For instance, in some examples, thecommunications interface 1545 includes one or more of an NFC tag, anRFID tag, a barcode and a QR code.

In various implementations, the medical device 1510 can be adefibrillator, patient monitor, defibrillator/monitor, an automatedcompression device, a therapeutic cooling device, an extracorporealmembrane oxygenation (ECMO) device, a ventilation device, combinationsthereof, or another type of medical device configured to couple to oneor more therapy delivery components to provide therapy to the patient.In an implementation, the medical device 1510 can be an integratedtherapy delivery/monitoring device within a single housing 1580. Thesingle housing 1580 can surround, at least in part, the therapy deliverycomponents and the monitoring components.

The patient interface device(s) 1560 can include one or more therapydelivery component(s) 1561 a and/or one or more sensor device(s) 1561 b.The medical device 1510 can be configured to couple to the one or moretherapy delivery component(s) 1561 a. In combination, the medical device1510 and the one or more therapy delivery components can providetherapeutic treatment to the patient 1518. In an implementation, themedical device 1510 can include or incorporate the therapy deliverycomponent(s) 1561 a. The therapy delivery component(s) 1561 a areconfigured to deliver therapy to the patient and can be configured tocouple to the patient. For example, the therapy delivery component(s)1561 a can include one or more of electrotherapy electrodes includingdefibrillation electrodes and/or pacing electrodes, chest compressiondevices (e.g., one or more belts or a piston), ventilation devices(e.g., a mask and/or tubes), drug delivery devices, etc. The medicaldevice 1510 can include the one or more therapy delivery component(s)1561 a and/or can be configured to couple to the one or more therapydelivery component(s) 1561 a to provide medical therapy to the patient.The therapy delivery component(s) 1561 a can be configured to couple tothe patient 1518. For example, a healthcare provider can attach theelectrodes to a patient 1518 and the medical device 1510 (e.g., adefibrillator or defibrillator/patient monitor) can provideelectrotherapy to the patient via the defibrillation electrodes. Theseexamples are not limiting of the disclosure as other types of medicaldevices, therapy delivery components, sensors, and therapy are withinthe scope of the disclosure.

The first medical device 1510 can be, for example, a therapeutic medicaldevice capable of delivering a medical therapy. For example, the medicaltherapy can be electrical therapy (e.g. defibrillation, cardiac pacing,synchronized cardioversion, diaphragmatic or phrenic nerve stimulation)and the first medical device 1510 can be a defibrillator, adefibrillator/monitor and/or another medical device configured toprovide electrotherapy. As another example, the medical therapy can bechest compression therapy for treatment of cardiac arrest and the firstmedical device 1510 can be a mechanical chest compression device such asa belt-based chest compression device or a piston-based chestcompression device. As other examples, the medical therapy can beventilation therapy, therapeutic cooling or other temperaturemanagement, invasive hemodynamic support therapy (e.g. ExtracorporealMembrane Oxygenation (ECMO)), etc. and the medical device 1510 can be adevice configured to provide a respective therapy. In an implementation,the medical device 1510 can be a combination of one or more of theseexamples. The therapeutic medical device can include patient monitoringcapabilities via one or more sensors. These types of medical therapy anddevices are examples only and not limiting of the disclosure.

The medical device 1510 can include, incorporate, and/or be configuredto couple to the one or more sensor(s) 1561 b which can be configured tocouple to the patient 1518. The sensor(s) 1561 b are configured toprovide signals indicative of sensor data (e.g., first sensor data) tothe medical device 1510. The sensor(s) 1561 b can be configured tocouple to the patient. For example, the sensor(s) 1561 b can includecardiac sensing electrodes, a chest compression sensor, and/orventilation sensors. The one or more sensors 1561 b can generate signalsindicative of physiological parameters of the patient 1518. For example,the physiological parameters can include one or more of at least onevital sign, an ECG, blood pressure, heart rate, pulse oxygen level,respiration rate, heart sounds, lung sounds, respiration sounds, tidalCO2, saturation of muscle oxygen (SMO2), arterial oxygen saturation(SpO2), cerebral blood flow, electroencephalogram (EEG) signals, brainoxygen level, tissue pH, tissue fluid levels, physical parameters asdetermined via ultrasound images, parameters determined vianear-infrared reflectance spectroscopy, pneumography, and/orcardiography, etc. Additionally or alternatively, the one or moresensors 1561 b can generate signals indicative of chest compressionparameters, ventilation parameters, drug delivery parameters, fluiddelivery parameters, etc.

In addition to delivering therapy to the patient, the therapy deliverycomponent(s) 1561 a can include, be coupled to, and/or function assensors and provide signals indicative of sensor data (e.g., secondsensor data) to the medical device 1510. For example, the defibrillationelectrodes can be configured as cardiac sensing electrodes as well aselectrotherapy delivery devices and can provide signals indicative oftransthoracic impedance, electrocardiogram (ECG), heart rate and/orother physiological parameters. As another example, a therapeuticcooling device can be an intravenous cooling device. Such a coolingdevice can include an intravenous (IV) device as a therapy deliverycomponent configured to deliver cooling therapy and sense the patient'stemperature. For example, the IV device can be a catheter that includessaline balloons configured to adjust the patient's temperature viacirculation of temperature controlled saline solution. In addition, thecatheter can include a temperature probe configured to sense thepatient's temperature. As a further example, an IV device can providetherapy via drug delivery and/or fluid management. The IV device canalso monitor and/or enable monitoring of a patient via blood samplingand/or venous pressure monitoring (e.g., central venous pressure (CVP)monitoring).

The medical device 1510 can be configured to receive the sensor signals(e.g., from the therapy delivery component(s) 1561 a and/or thesensor(s) 1561 b) and to process the sensor signals to determine andcollect the patient data. The patient data can include patient datawhich can characterize a status and/or condition of the patient (e.g.,physiological data such as ECG, heart rate, respiration rate,temperature, pulse oximetry, non-invasive hemoglobin parameters,capnography, oxygen saturation (SpO2), end tidal carbon dioxide (EtCO2),invasive blood pressure (IBP), non-invasive blood pressures (NIBP),tissue pH, tissue oxygenation, Near Infrared Spectroscopy (NIRS)measurements, etc.). Additionally or alternatively, the patient data cancharacterize the delivery of therapy (e.g., chest compression data suchas compression depth, compression rate, etc.) and/or the patient datacan characterize a status and/or condition of the medical equipment usedto treat the patient (e.g., device data such as shock time, shockduration, attachment of electrodes, power-on, etc.).

The components of 1520, 1521, 1530, 1544, 1545, and 1555 of the medicaldevice 1510 are communicatively coupled (directly and/or indirectly) toeach other for bi-directional communication.

Although shown as separate entities in FIG. 15 , the one or more of thecomponents of the device 1510 can be combined into one or more discretecomponents and/or can be part of the processor 1520. The processor 1520and the memory 1521 can include and/or be coupled to associatedcircuitry to perform the functions described herein.

In an implementation, the devices 1510 can be a therapeutic medicaldevice configured to deliver medical therapy to the patient 1518. Thus,the device 1510 can optionally include the therapy delivery controlmodule 1555. For example, the therapy delivery control module 1555 canbe an electrotherapy delivery circuit that includes one or morecapacitors configured to store electrical energy for a pacing pulse or adefibrillating pulse. The electrotherapy delivery circuit can furtherinclude resistors, additional capacitors, relays and/or switches,electrical bridges such as an H-bridge (e.g., including a plurality ofinsulated gate bipolar transistors or IGBTs), voltage measuringcomponents, and/or current measuring components. As another example, thetherapy delivery control module 1555 can be a compression device such asan electro-mechanical controller configured to control a mechanicalcompression device. As a further example, the therapy delivery controlmodule 1555 can be an electro-mechanical controller configured tocontrol drug delivery, temperature management, ventilation, and/or othertype of therapy delivery. Alternatively, some examples of the medicaldevice 1510 cannot be configured to deliver medical therapy to thepatient 1518 but can be configured to provide patient monitoring and/ordiagnostic care.

The medical device 1510 (e.g., a first medical device) can incorporateand/or be configured to couple to one or more patient interfacedevice(s) 1560. The patient interface device(s) 1560 can include one ormore therapy delivery component(s) 1561 a and one or more sensor(s) 1561b. The one or more therapy delivery component(s) 1561 a and the one ormore sensor(s) 1561 b sensor can provide one or more signals to themedical device 1510 via wired and/or wireless connection (s).

The one or more therapy delivery components 1561 a can includeelectrotherapy electrodes (e.g., the electrotherapy electrodes 1566 a),ventilation device(s) (e.g., the ventilation devices 1566 b),intravenous device(s) (e.g., the intravenous devices 1566 c),compression device(s) (e.g., the compression devices 1566 d), etc. Forexample, the electrotherapy electrodes can include defibrillationelectrodes, pacing electrodes, and/or combinations thereof. Theventilation devices can include a tube, a mask, an abdominal and/orchest compressor (e.g., a belt, a cuirass, etc.), etc. and combinationsthereof. The intravenous devices can include drug delivery devices,fluid delivery devices, and combinations thereof. The compressiondevices can include mechanical compression devices such as abdominalcompressors, chest compressors, belts, pistons, and combinationsthereof. In various implementation, the therapy delivery component(s)1561 a can be configured to provide sensor data and/or be coupled toand/or incorporate sensors. For example, the electrotherapy electrodescan provide sensor data such as transthoracic impedance, ECG, heartrate, etc. Further the electrotherapy electrodes can include and or becoupled to a chest compression sensor. As another example, theventilation devices can be coupled to and/or incorporate flow sensors,gas species sensors (e.g., oxygen sensor, carbon dioxide sensor, etc.),etc. As a further example, the intravenous devices can be coupled toand/or incorporate temperature sensors, flow sensors, blood pressuresensors, etc. As yet another example, the compression devices can becoupled to and/or incorporate chest compression sensors, patientposition sensors, etc. The therapy delivery control module 1555 can beconfigured to couple to and control the therapy delivery component(s)1561 a.

In various implementations, the sensor(s) 1561 b can include one or moresensor devices configured to provide sensor data that includes, forexample, but not limited to electrocardiogram (ECG), blood pressure,heart rate, pulse oxygen level, respiration rate, heart sounds, lungsounds, respiration sounds, tidal CO2, saturation of muscle oxygen(SMO2), arterial oxygen saturation (SpO2), cerebral blood flow,electroencephalogram (EEG) signals, brain oxygen level, tissue pH,tissue fluid levels, images and/or videos via ultrasound, laryngoscopy,and/or other medical imaging techniques, near-infrared reflectancespectroscopy, pneumography, cardiography, and/or patient movement.Images and/or videos can be two-dimensional or three-dimensional.

The sensor(s) 1561 b can include sensing electrodes (e.g., the sensingelectrodes 1562), ventilation sensors (e.g., the ventilation sensors1564), temperature sensors (e.g., the temperature sensor 1567), chestcompression sensors (e.g., the chest compression sensor 1568), etc. Forexample, the sensing electrodes can include cardiac sensing electrodes.The cardiac sensing electrodes can be conductive and/or capacitiveelectrodes configured to measure changes in a patient'selectrophysiology, for example to measure the patient's ECG information.In an implementation, the sensing electrodes can be configured tomeasure the transthoracic impedance and/or a heart rate of the patient1518. The ventilation sensors can include spirometry sensors, flowsensors, pressure sensors, oxygen and/or carbon dioxide sensors such as,for example, one or more of pulse oximetry sensors, oxygenation sensors(e.g., muscle oxygenation/pH), O2 gas sensors and capnography sensors,and combinations thereof. The temperature sensors can include aninfrared thermometer, a contact thermometer, a remote thermometer, aliquid crystal thermometer, a thermocouple, a thermistor, etc. and canmeasure patient temperature internally and/or externally. The chestcompression sensor can include one or more motion sensors including, forexample, one or more accelerometers, one or more force sensors, one ormore magnetic sensors, one or more velocity sensors, one or moredisplacement sensors, etc. The chest compression sensor can be, forexample, but not limited to, a compression puck, a smart-phone, ahand-held device, a wearable device, etc. The chest compression sensorcan be configured to detect chest motion imparted by a rescuer and/or anautomated chest compression device (e.g., a belt system, a pistonsystem, etc.). The chest compression sensor can provide signalsindicative of chest compression data including displacement data,velocity data, release velocity data, acceleration data, compressionrate data, dwell time data, hold time data, blood flow data, bloodpressure data, etc. In an implementation, the sensing electrodes and/orthe electrotherapy electrodes can include or be configured to couple tothe chest compression sensor.

Referring to FIG. 16 , an example of a medical device with anoperational interface is shown. The medical device 1510 is shown in FIG.16 as a patient monitor/defibrillator. This configuration of the medicaldevice 1510 is an example only and not limiting of the disclosure. Invarious implementations, the medical device 1510 can be a defibrillator,patient monitor, defibrillator/monitor, an automated compression device,a therapeutic cooling device, an extracorporeal membrane oxygenation(ECMO) device, a ventilation device, combinations thereof, or anothertype of medical device configured to couple to one or more therapydelivery components to provide therapy to the patient. In animplementation, the medical device 1510 can be an integrated therapydelivery/monitoring device that includes a single housing. The singlehousing can surround, at least in part, the therapy delivery componentsand the monitoring components. In an implementation, the medical device1510 can be a modular therapy delivery/monitoring device.

The medical device 1510 can include one or more output or input/outputdevices, for example, a display screen 1615. A processor of the medicaldevice 1510 can control the display screen 1615 to selectively displaythe operational interface 1635. The operational interface 1635 as shownin FIG. 16 is an example only and elements can be rearranged, combined,altered, or deleted. As discussed in further detail below, selectivedisplay refers to the ability of the processor to select amongst variousavailable display modes which can include an operational interface onlydisplay mode.

The operational interface 1635 can provide patient data received by themedical device 1510 from the patient interface device(s) 1560 (e.g., thetherapy delivery component(s) 1561 a and/or from the sensor(s) 1561 b).For example, the medical device 1510 can be configured to couple to thepatient interface device(s) 1560 via the one or more connection ports1675. The operational interface 1635 can provide the patient data inreal-time as the signals are received and processed by the processor1520 of the medical device 1510.

The therapy delivery component(s) 1561 a are configured to delivertherapy to the patient and can be configured to couple to the patient.For example, the therapy delivery component(s) 1561 a can include one ormore of electrotherapy electrodes including defibrillation electrodesand/or pacing electrodes, chest compression devices, ventilationdevices, drug delivery devices, etc. In addition to delivering therapyto the patient, the therapy delivery component(s) 1561 a can include, becoupled to, and/or function as sensors and provide signals indicative ofsensor data (e.g., first sensor data) to the medical device 1510. Forexample, the therapy delivery component(s) 1561 a can be defibrillationand/or pacing electrodes and can provide signals indicative oftransthoracic impedance, electrocardiogram (ECG), heart rate and/orother physiological parameters.

The sensor(s) 1561 b are configured to provide signals indicative ofsensor data (e.g., second sensor data) to the medical device 1510. Thesensor(s) 1561 b can be configured to couple to the patient. Forexample, the sensor(s) 1561 b can include cardiac sensing electrodes, achest compression sensor, and/or ventilation sensors.

The medical device 1510 can be configured to receive the sensor signals(e.g., from the therapy delivery component(s) 1561 a and/or thesensor(s) 1561 b) indicative of patient data for the patient andconfigured to process the sensor signals to determine and collect thepatient data. The patient data can include patient data which cancharacterize a status and/or condition of the patient (e.g.,physiological data such as ECG, heart rate, pulse oximetry, non-invasivehemoglobin parameters, capnography, oxygen and CO2 concentrations in theairway, invasive and non-invasive blood pressures, tissue pH, tissueoxygenation, near infra-red spectroscopy, etc.). Additionally oralternatively, the patient data can characterize the delivery of therapy(e.g., chest compression data such as compression depth, compressionrate, etc.) and/or the patient data can characterize a status and/orcondition of the medical equipment used to treat the patient (e.g.,device data such as shock time, shock duration, attachment ofelectrodes, power-on, etc.).

In addition to the display screen 1615, the medical device 1510 caninclude one or more other output devices such as, for example, a speaker1670. The processor 1520 can be configured to control the speaker 1670to provide audible instructions, a metronome (e.g., a chest compressionmetronome), feedback, and/or physiological information for a user of themedical device 1510. The medical device 1510 can further include devicestatus indicators and/or device operation controls. For example, devicestatus indicators can include a power-on indicator 1651, a batterycharge indicator 1652, and/or a device ready indicator 1653. The deviceoperation controls can include a power-on control 1660, a pacer modecontrol 1661, a heart rhythm analyze control 1662, a defibrillationenergy selection control 1663, a charge control 1664, a shock deliverycontrol 1665, a general mode control 1666, an alarm control 1671, one ormore display navigation controls 1672, and a sensor control 1674.Activation of the sensor control 1674 can cause an associated patientdata sensor to capture patient data and provide the data to the medicaldevice 1510. The display screen 1615 can provide the captured patientdata. For example, activation of the sensor control 1674 can cause ablood pressure sensor to measure the patient's blood pressure and cancause the operational interface 1635 to display the measured bloodpressure in response to activation of the sensor control 1674. Themedical device 1510 can include one or more soft-keys 1650 a, 1650 b,1650 c, 1650 d, one or more soft-key labels 1651, and/or an NFC tag1680. The NFC tag 1680 can enable the medical device 1510 tocommunicatively couple with another device, such as a mobile computingdevice or a wireless enabled medical device accessory as describedherein.

1-135. (canceled)
 136. A defibrillation electrode for use with aplurality of defibrillation devices, the defibrillation electrodecomprising: a connector configured to operably couple the defibrillationelectrode to at least one of a first defibrillation device and a seconddefibrillation device; a skin contacting portion configured to contactskin of a patient; and a housing comprising non-volatile memory andassociated circuitry, the non-volatile memory and associated circuitryconfigured to: store a device identifier readable by the firstdefibrillation device and the second defibrillation device to identifythe defibrillation electrode, receive medical treatment information fromthe first defibrillation device via the connector, the medical treatmentinformation comprising at least one of: patient physiological data,patient characteristic data, and rescuer performance data, record themedical treatment information, and transfer, upon detecting anelectrical connection to the second defibrillation device, the medicaltreatment information to the second defibrillation device.
 137. Thedefibrillation electrode of claim 136, wherein the medical treatmentinformation is recorded by the first defibrillation device duringmonitoring of a patient prior to and/or during treatment of the patient.138. The defibrillation electrode of claim 136, wherein the deviceidentifier comprises type and serial information for at least one of thefirst defibrillation device and the second defibrillation device torecord.
 139. The defibrillation electrode of claim 136, wherein thedevice identifier provides for authentication with at least one of thefirst defibrillation device and the second defibrillation device forsecure transfer of the medical treatment information.
 140. Thedefibrillation electrode of claim 136, wherein the non-volatile memoryand associated circuitry is configured to receive timing information ofthe medical treatment information from the first defibrillation devicevia the connector.
 141. The defibrillation electrode of claim 140,wherein the timing information of the medical treatment informationcomprises a time at which the medical treatment information was recordedby the first defibrillation device.
 142. The defibrillation electrode ofclaim 141, further comprising timing circuitry operable to independentlytrack time elapsed since the time at which the medical treatmentinformation was recorded by the first defibrillation device.
 143. Thedefibrillation electrode of claim 136, wherein the non-volatile memoryand associated circuitry is configured to record the medical treatmentinformation from the first defibrillation device before the transfer ofthe medical treatment information to the second defibrillation device.144. The defibrillation electrode of claim 143, wherein the non-volatilememory and associated circuitry is configured to record the medicaltreatment information from the first defibrillation device when theconnector is engaged with the first defibrillation device, and transferof the medical treatment information to the second defibrillation devicewhen the connector is engaged with the second defibrillation device.145. The defibrillation electrode of claim 136, wherein the medicaltreatment information further comprises summary information recordingcritical patient events requiring treatment, shock information for anydelivered shocks, pacing summary data, and indications of alarm events.146. The defibrillation electrode of claim 136, configured to beoperably removed from a first of the plurality of defibrillation devicesand operably coupled to a computing device.
 147. The defibrillationelectrode of claim 136, wherein the non-volatile memory and theassociated circuitry are further configured to: determine whether thedefibrillation electrode is within a proximity of a remote device;establish, in response to a determination that the defibrillationelectrode is within the proximity, an operable connection with theremote device; and transfer at least a portion of the medical treatmentinformation to the remote device.
 148. The defibrillation electrode ofclaim 147, wherein the transfer of at least a portion of the medicaltreatment information to the remote device occurs automatically when theoperable connection is established between the defibrillation electrodeand the remote device.
 149. The defibrillation electrode of claim 147,wherein the transfer of at least a portion of the medical treatmentinformation to the remote device occurs in response to a user-providedrequest to transfer subsequent to establishing the operable connectionbetween the defibrillation electrode and the remote device.
 150. Thedefibrillation electrode of claim 136, wherein to record the medicaltreatment device information to the memory comprises encrypting themedical treatment information prior to recording to the memory.
 151. Thedefibrillation electrode of claim 136, wherein the patient physiologicaldata comprises one or more of patient ECG data, heart rate data, ECGwaveform data, end-tidal CO2 data, CO2 waveform data, pulse oximetrydata, blood oxygenation data, blood pressure data, and respiratory ratedata.
 152. The defibrillation electrode of claim 136, wherein thepatient characteristic data comprises one or more of patient heightdata, patient weight data, patient gender indication, patient physicalmeasurement data, and patient history information.
 153. Thedefibrillation electrode of claim 136, wherein the rescuer performancedata comprises one or more of chest compression performance data,ventilation performance data, rescuer treatment information, and druginfusion information.
 154. The defibrillation electrode of claim 136,wherein the medical treatment information comprises device operationaldata comprising one or more of defibrillation shock deliveryinformation, defibrillation shock energy information, and ventilatorflow information.
 155. The defibrillation electrode of claim 136,wherein the connector is configured to be operably coupled to thedefibrillation device during a first treatment event and the at leastone of a processor operably coupled to the memory and software isfurther configured to record at least one parameter associated with thefirst treatment event to the memory.
 156. The defibrillation electrodeof claim 155, wherein the connector is further configured to bedecoupled from the defibrillation device and operably coupled to asecond defibrillation device such that the medical treatment informationstored on the memory is accessible to the second defibrillation device.157. The defibrillation electrode of claim 136, wherein the memory isconfigured to be operably removed from the defibrillation electrode andoperably coupled to a second defibrillation electrode.
 158. Thedefibrillation electrode of claim 136, wherein the memory is configuredto be operably removed from the defibrillation electrode and operablycoupled to a computing device.
 159. The defibrillation electrode ofclaim 136, wherein the memory is integrated into the connector.
 160. Thedefibrillation electrode of claim 136, wherein at least a portion of theskin contacting portion is further configured to deliver adefibrillation shock to the patient during treatment. 161-181.(canceled)